Ive run into an interesting (rather annoying) error while using Visual Studio to debug a mixed WPF/CLR/Unmanaged native c++ project, this error occurs only in Windows XP. It would seem that I have a memory corruption occuring within the program, the scope of which is much too large to post here. The problem that I am having is that when the crash occurs in the program, it simply exits without the VS debugger attempting to locate an exception, I assume because none is thrown. The program exit code is really the only information I have to go on, and its just the minimum int value.
Has anyone encountered this and might be able to point me in the right direction as far as what it means?
EDIT:
Continuing to investigate the problem, Ive discovered that I can sometimes get a stack trace and an exception as opposed to a straight program exit. The trace brings me to a vector allocation (push). In the scenario where the program just exits, this is still the last line executed. I assume that I have corrupt memory somewhere, though I was hoping that the fact that this usually manifests itself as a program dump and not an exception would be able to help point me in the right direction.
The program ' [4268] Project4.exe ' has exited with code 0 (0x0). Exited with code 0 means there was no error. What is your question? Please show the code of your program so we can see what it is doing.
It could be a stray __debugbreak () you left in your code, it could be triggered by a wild jump when the program state got corrupted. You'll need to debug it. If you can't easily repro it on your dev machine then you'll need a minidump from the failing machine.
The thread 0x754 has exited with code -1073741701 (0xc000007b). The thread 0x3a00 has exited with code -1073741701 (0xc000007b). The program '[5456] myprogram.exe' has exited with code -1073741701 (0xc000007b).
//
// MessageId: STATUS_BREAKPOINT
//
// MessageText:
//
// {EXCEPTION}
// Breakpoint
// A breakpoint has been reached.
//
#define STATUS_BREAKPOINT ((NTSTATUS)0x80000003L)
The program landed on an INT3 instruction and triggered a breakpoint. But no debugger present so that terminates the program. It could be a stray __debugbreak() you left in your code, it could be triggered by a wild jump when the program state got corrupted.
You'll need to debug it. If you can't easily repro it on your dev machine then you'll need a minidump from the failing machine.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With