All geek questions in one place

First time exception at 0x782260ec in xxx.exe: 0xC0000005: access violation

My application crashes after a while, but I can not find any template. I was able to get a dump. The application runs on Windows Mobile 6.5. It is written in C #. It uses the Imaging API , PInvoks and many threads.

When I debugged this dump with Visual Studio 2008, on the output it displayed "Exception from first chance in 0x782260ec in xxx.exe: 0xC0000005: access violation"

Call Stack shows 2 entries. But I cannot match any of them to call from my code.

windbg.exe indicates that this error occurs in the netcfagl3_5.dll file

Are there any special methods for analyzing dump files from Windows Mobile?

+4
source share
3 answers

0xC0000005: Access violation means one of your p / invokes is incorrect. The call was attempted to be written to a memory area to which it does not have access (which is typical if the definition is incorrect).

Should your dump contain a stack trace?

+1
source

A “random exception” usually means an exception that is handled by user code. If you use Vosual Studio and the Windows Mobile emulator for debugging, you can turn off exception handling. Go to Debug> Exceptions and check the Thrown column for Win32 exceptions. Then run the program and try to crash again.

When debugging starts, it stops execution and is interrupted by the debugger when it falls into this "first chance exception", allowing you to see what causes it and see if it is related.

The library 'netcfagl3_5.dll' is part of .NET CF, not your code, so you cannot match debugging characters.

0
source

You will need to download windbg, Visual Studio 2008 will not debug Post Mortem.NET.

If your development machine is 64-bit, see " How to use Windbg to debug a dump of a 32-bit .NET application running on an x64 machine "

Otherwise, see Publish Mortem Debug on Windows Mobile using WinDbg . also do some searches in the "Windows Mobile Post Mortem Debug".

The best (by far) and easiest way, however, is to reproduce this problem while working in the debugger. Debugging post mortem.net is NOT easy.

-PaulH

0
source

Source: https://habr.com/ru/post/1380210/

More articles:


All Articles