![]() Minidump doesn't have an exception context Is this the main entry point of my application or does this have to do with some external Kalmbach. What can I do to further analyse the issue/find the cause?.Can IL-Code generated with Reflection.Emit result in this kind of error?.Maybe someone could help me to interpret this data and/or give me some hints what else I can try? When I open the dump with Visual Studio there is also written no exception found. I looks like this is really the entry point of the application because of the CoreExeMain Exports? So not so much useful informations here, or? Only that the problem occurs on native code level as far as I interpreted it.Īnd just for completeness. Is this correct? So I am expecting the following command to display the disassembly from the function at MyProgram 0圆a9e, see call stack above. ![]() I read somewhere that you can take the address of the column RetAddr and pass it to uf to see what the function at this point is doing. The next part I am pretty unsure if it is correct what I did. ![]() Defaulted to export symbols for sysfer.dll. *** ERROR: Symbol file could not be found. sympath SRV*C:\Symbols* C:\PathToMatchingPDBs\ForTheProgram I am not an expert on native programming and only know some basics about WinDbg. We already created a full memory dump with ProcDump flag -ma when the windows error reporting dialog was open. I found out that 0xc0000005 is an access violation. The error report from windows event log looks something like this (application and module names omitted and I translated the entries from German): Exceptioncode: 0xc0000005 Third Party native modules used SQL CE 3.5, and others.NET x86 application (not An圜PU not ASP.NET) Windows Server 2012 圆4 (Virtual Machine running on a blade system).It randomly on closing produces a native access violation (so not the.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |