Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 315
  • Last Modified:

Debug : Access violation at address XXXXXXXXX

The application I am working on is built using all OCXs what contains UI and SOAP interface. The most issues I receive have no more information except Access violation at address XXXXXXXXX and sometimes it is really hard to find the code location what raises the exception.

What I want is the way to find out the exact code what raises the exception. Is it possible to find the source code using the above error message. I mean by using the address shown in the error. Is it is the how I can? I tried with looking at CPU window but could not get much.
0
atul_parmar
Asked:
atul_parmar
  • 3
  • 2
1 Solution
 
atul_parmarAuthor Commented:
I gone through
http://delphi.about.com/od/objectpascalide/l/aa052201b.htm
but I it did not helped me much.
0
 
2266180Commented:
those addresses are memory addresses so they don't help much.

you could try madshi's components and adding debug info to everything and compile with that. I myself never did this, but some say this helps.
0
 
David_WardCommented:
Yep, go with ciuly, MadExcept can be your very good friend.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
atul_parmarAuthor Commented:
Does this means that with Delphi (only) it is not possible. Coz' our company's policy a bit strong and requires lot of thigs to do and after all it is not guaranteed that it can be approved.

I understand that the address shown in the message is memory address and can vary each time. But I still hope that there must be some way to do it.
0
 
2266180Commented:
well .. logging is the anser to that. but that is not so accurate, but is helpfull in locating the error. you can also try adding some try/excepts and maybe even logging the stacktrace (you will again have to use some 3rd party tools that are basically the same as madhi's - or write your own).
but all this is pretty hard to implement in the first place (from a time perspective) and it takes some time to debug. optimal would be some loging mechanism that logs when you enter a function, and when you leave it. so you can trace the execution like that, but you will have a lot of lines to write. best way is using some stack trace components: madhi's madexcept recommended.
0
 
atul_parmarAuthor Commented:
Thank you Ciuly.

I agree that to simplify my life I will have to go with MadExpert or do it with my way. :)
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now