MinGW + MSYS + Eclipse CDT shared libs: The application failed to initialize properly (0xc0000005).
in [wxWindows]
|
Prev: MinGW + MSYS + Eclipse CDT shared libs: The application failed to initialize properly (0xc0000005).
Next: MinGW + MSYS + Eclipse CDT shared libs: The application failed to initialize properly (0xc0000005).
From: Lars Uffmann on 8 Jun 2010 10:40 Lars Uffmann wrote: > Loaded "NTDLL.DLL" at address 0x7C900000. Successfully hooked module. > [..] > Second chance exception 0xC0000005 (Access Violation) occurred in > "NTDLL.DLL" at address 0x7C966668. Doing the math here gets me to the violation occuring at address 0x7c966668 - 0x7c900000 = 0x66668 inside NTDLL.DLL, being seemingly within the memory area of the function RtlRaiseStatus (entry point 0x66642) and just 9 bytes before the start of function RtlRandom (entry point 0x66671) - more to google for me, as to how RtlRaiseStatus can cause an exception like that, and I guess this isn't really wxWidgets related anymore, then... Help appreciated nevertheless... Best Regards, Lars
From: Lars Uffmann on 8 Jun 2010 11:29 With mingw32 gdb on the msys command line, I get this message: "During startup program exited with code 0xc0000005." When I try to backtrace, gdb answers "No stack." I linked a debug configuration in Eclipse, using Linux GCC toolchain (MSYS make). So from my understanding, there should be debug information in the executable (being 800kByte instead of the Release's 100kByte). Any more ideas? Lars
From: Rüdiger Ranft on 9 Jun 2010 03:43
Lars Uffmann schrieb: > R�diger Ranft wrote: >> You can examine the dependencies of your program with the Microsoft >> "dependency walker". Look for errors in the output, and which dll causes > > Will > http://www.dependencywalker.com/ > do the trick? I didn't know Microsoft had it's own... They are the same. > Dependency Walker output: > ------------ > Started "SAMPLEMINIMAL.EXE" (process 0xF74) at address 0x00400000. > Successfully hooked module. > Loaded "NTDLL.DLL" at address 0x7C900000. Successfully hooked module. > Loaded "KERNEL32.DLL" at address 0x7C800000. Successfully hooked module. > DllMain(0x7C900000, DLL_PROCESS_ATTACH, 0x00000000) in "NTDLL.DLL" called. > DllMain(0x7C900000, DLL_PROCESS_ATTACH, 0x00000000) in "NTDLL.DLL" > returned 1 (0x1). > > [..left out some other successful loads..] > > Loaded "SHLWAPI.DLL" at address 0x77F60000. Successfully hooked module. Welcome in dll hell. Is the build machine the same as the execution machine? Can you execute an example program on the build machine? I got a similar error once when i accidentally copied a windows runtime lib to another windows version. bye Rudi |