first chance exception in my.exe (ntdll.dll)

Started by
0 comments, last by outRider 22 years, 7 months ago
Whenever I run my app everything works just fine, there are no problems. But, when I run it through VC''s debugger (Go command) I get the following output in the debug window. Loaded ''C:\WINNT\System32\ntdll.dll'', no matching symbolic information found. Loaded ''C:\WINNT\system32\KERNEL32.DLL'', no matching symbolic information found. Loaded ''C:\WINNT\system32\USER32.DLL'', no matching symbolic information found. Loaded ''C:\WINNT\system32\GDI32.DLL'', no matching symbolic information found. Loaded ''C:\WINNT\system32\OPENGL32.DLL'', no matching symbolic information found. Loaded ''C:\WINNT\system32\msvcrt.dll'', no matching symbolic information found. Loaded ''C:\WINNT\system32\ADVAPI32.DLL'', no matching symbolic information found. Loaded ''C:\WINNT\system32\rpcrt4.dll'', no matching symbolic information found. Loaded ''C:\WINNT\system32\glu32.dll'', no matching symbolic information found. Loaded ''C:\WINNT\system32\ddraw.dll'', no matching symbolic information found. Loaded ''C:\WINNT\system32\dciman32.dll'', no matching symbolic information found. Loaded ''C:\WINNT\system32\apitrap.dll'', no matching symbolic information found. Loaded ''C:\WINNT\system32\psapi.dll'', no matching symbolic information found. First-chance exception in Siege.exe (NTDLL.DLL): 0xC0000005: Access Violation. Loaded ''C:\WINNT\system32\nvdesk32.dll'', no matching symbolic information found. Loaded ''C:\WINNT\system32\nvoglnt.dll'', no matching symbolic information found. Loaded ''C:\WINNT\system32\mcd32.dll'', no matching symbolic information found. The thread 0x144 has exited with code 0 (0x0). The program ''G:\MYPROJECTS\Siege\Debug\Siege.exe'' has exited with code 0 (0x0). Now, this isn''t a big deal, theres nothing bad that happens when running the exe, but I don''t want it to lead to problems later on. I haven''t been able to isolate the problem, I''m using OpenGL so the normal Win32 stuff I''m doing (creating window) doesn''t seem to be causing it. I don''t know much about exceptions so what a First-chance exception in a dll is is beyond me (I''m thinking maybe a leak somewhere). Perhaps someone can fill me in, I''d appreciate it. ------------ - outRider -
Advertisement
You do not need to worry about that.

http://support.microsoft.com/support/kb/articles/Q105/6/75.asp

This topic is closed to new replies.

Advertisement