Geek asks and answers

The program exited with code -2147483645

Ive encountered an interesting (rather annoying) error when using Visual Studio to debug a mixed draft open source script WPF / CLR / Unmanaged, this error only occurs in Windows XP. It would seem that in my memory there is a corruption of memory, the volume of which is too large for publication here. The problem that I am facing is that when an accident occurs in the program, it just exits without the VS debugger, trying to find an exception, I assume that no one is thrown. The program exit code is really the only information I have to continue with, and its minimum int value.

Has anyone come across this and could point me in the right direction as far as possible?

EDIT:

Continuing to investigate the problem, Ive discovered that sometimes I can get a stack trace and an exception, as opposed to directly exiting the program. The trace leads me to a vector distribution (push). In a scenario, when the program just exits, it is still the last line executed. I suppose I have a corrupt memory somewhere, although I was hoping that the fact that this usually manifests itself as a program dump rather than an exception can help me point me in the right direction.

+5
source share
1 answer
//
// MessageId: STATUS_BREAKPOINT
//
// MessageText:
//
// {EXCEPTION}
// Breakpoint
// A breakpoint has been reached.
//
#define STATUS_BREAKPOINT                ((NTSTATUS)0x80000003L)

INT3 . , . __debugbreak(), , , .

. dev, - .

+6

More articles:


All Articles