Link to home
Create AccountLog in
Avatar of HankCash
HankCashFlag for United States of America

asked on

Homegrown software giving "Access violation at" error in DLL.

We have a homegrown software, developed in C,  that is giving the following error to one of our customers.

Access violation at address 0035403D in module '*******.dll'.  Read of address 00000182.

The "at address" and "of address" change each time the error is generated.

The Customer Service department and I (IT Department) are left to troubleshoot this problem because there are no programers available to help.  I throw myself at your mercy because I really don't even know where to begin to figure this out.  

We have been able to recreate a situation in our lab where we can get the error to generate somewhat reliably.  The errors build up continually until eventually the application crashes.

I have installed Debugging Tools for Windows and have a complete dump of the application memory (116MB) but don't know what to do with it.  Any help about how to best pursue this issue, given lack of in house programing help, is greatly appreciated.
Avatar of jkr
jkr
Flag of Germany image

Do you have the source code of the application in question? If so, try reproducing the error while running under the debugger as a debug build. This will take you right to the faulting line of code.
Avatar of HankCash

ASKER

I've been told that the development computer had a catastophic harddrive error after sitting idol for years though this was never brought to my attention at the time.  Though my knowledge is limited, it seems the source code should be available in Visual Source Safe rather than being dependent on a single PC.  Unfortunately, I don't know hot to look for the source code.
Hm, that's a catch-22 - without source code, you won't be able to find the reason for the crash, and even if you could, you can't fix it without the code...
Because of the lack of the code and programming support, the hope is to isolate the problem and advise our customer how to work around it.
That's going to be more than difficult. Without the actual code, you won't even know what the application is doing at the time of the crash. Do you at least know what compiler was used to create the executable?
I'm trying to unravel the mystery of the computer and code. It's a very delicate situation.
SOLUTION
Avatar of jkr
jkr
Flag of Germany image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
jkr-
You have been very helpful and I greatly appreciate it.  I'm attaching a file that gives a full rundown of what is going on from a support perspective rather than a programmers perspective.  If you are willing, please take a look.

Note: My opinion is that the fact that we have not been able to generate the error on the virtualized version of Windows XP does not reveal anything of substance.
VM-25-TL1-Problem-021313-JCG.ppt
ASKER CERTIFIED SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
I could not find extensions listed for the project in question, though I did find them for other projects.  This leads me to believe that this software was not developed using standard ops.  This would explain why we are getting so little help from the engineers as they are trying to keep this under wraps.