gbmgeor
asked on
Exception Problems
I have some code (>100,000 lines) that occasionally throughs up the following error on a NT 3.51 (SP5) system.
myapp.exe - Application Error
Exception Unknown - software exception (0xC000008) occured in the application at location 0x77FC02CD.
The location is in NTDLL.DLL, and the exception (0xC0000008) indicates that an invalid handle has been referenced.
My problem is that when this popup box appears, there is no option to debug (only option in OK), even though I have setup the system debugber option in AEDebug registry key. Other exceptions on this system do allow you to debug.
So, my questions are :-
1) Why no CANCEL option, so that I can debug (or capture Dr Watson output)?
2) What can cause this error ? If I write a quick program that does a CloseHandle(0xabababab), then under the debugger this causes a First Chance exception that is handled (by NTDLL.DLL ?). So, when I run this normally, no exceptions are thrown.
Because this happens at random, involving thousands of executions of this application, I need some way of gathering a stack-back trace, or at least some indication of the type of scenario that could cause this.
myapp.exe - Application Error
Exception Unknown - software exception (0xC000008) occured in the application at location 0x77FC02CD.
The location is in NTDLL.DLL, and the exception (0xC0000008) indicates that an invalid handle has been referenced.
My problem is that when this popup box appears, there is no option to debug (only option in OK), even though I have setup the system debugber option in AEDebug registry key. Other exceptions on this system do allow you to debug.
So, my questions are :-
1) Why no CANCEL option, so that I can debug (or capture Dr Watson output)?
2) What can cause this error ? If I write a quick program that does a CloseHandle(0xabababab), then under the debugger this causes a First Chance exception that is handled (by NTDLL.DLL ?). So, when I run this normally, no exceptions are thrown.
Because this happens at random, involving thousands of executions of this application, I need some way of gathering a stack-back trace, or at least some indication of the type of scenario that could cause this.
Select OK, then check out %SYSTEMROOT%\drwtsn32.log
ASKER
Dr Watson log is not generated when you click OK.
Were there any other log files in "c:\winnt\"?
Please bear with me, what I told you worked in NT4.0; I don't know what differences there may be in 3.51.
Run drwtsn32.exe; it may have a different path set for the log file.
Please bear with me, what I told you worked in NT4.0; I don't know what differences there may be in 3.51.
Run drwtsn32.exe; it may have a different path set for the log file.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thui, I've looked into these in the past, but I was under the impression that the default behaviour would be the option to trigger the default system debugger. What I would really like are some scenarios that could cause this exception.