Re: Finding the source code corresponding to an application error

Thanks! I'll try that.

- A
"Oleg Starodumov" <com-dot-debuginfo-at-oleg> wrote in message
news:OoL92QfDGHA.412@xxxxxxxxxxxxxxxxxxxxxxx
>
>> My program crshed and the Windows Event Log error was:
>> Application popup: MCSCRE.EXE - Application Error : The instruction at
>> "0x7c910f29" referenced memory at "0x00000000".
>> The memory could not be "read".
>> How do I find out which line of source code corresponds to this address?
>>
>
> In general, you can use one of the approaches described in this article:
> http://www.cygnus-software.com/papers/release_debugging.html
>
> In this particular case, the crash most likely occurred in one of system
> DLLs,
> so the address itself is not enough to find out what part of the
> application's code
> is responsible for that - call stack information is needed, e.g. from a
> minidump.
> If you can find out which DLL the address 0x7c910f29 on the target system
> belongs to, you might be able to guess what parts of your code could call
> it.
> In particular, if it was ntdll.dll, heap corruption would be one of the
> first suspects.
>
> Regards,
> Oleg
> [VC++ MVP http://www.debuginfo.com/]
>
>
>


.

Relevant Pages
Loading