G
Guest
My application is crashing in a weird way. I'm using .NET Forms called from
native code. The form pop-up correctly and run correctly UNTIL I try to close
the form. The close procedure basically is just a cleanup destructor written
in C++
that works fine the first two times it's used. The third time it appears to
work
ok as well but the base application takes an R6025 trap. Debugging this has
been a nightmare. I do single step in the debugger in the forms code and see
no
problems. I've added code to use _set_purecall_handler() in the wrapper
code that creates the .NET Form object but it never gets called unless I
force it.
When I force it, the base application appears to die in a consistent manner.
The stack trace I get when this occurs is:
msvc71d.dll!_NMSG_Write(rterrnum=25)
msvc71d.dll!_amsg_exit(rterrnum=25)
msvc71d.dll!_purecall()
mscorwrks.dll!CorExitProcess()
1b28a04e()
All of the stack looks ok except the CorExitProcess() function which I can not
get any documentation on or for that matter any related crash info on.
I need to know what is going on so I can fix what I'm doing wrong.
I do have virtual functions in the code but I'm pretty sure that they
aren't being called unless some magic in the constructors are causing
it to happen implicitly, there is no explicit calls in the constructors.
All I do is create the form, then click on my cancel button to cause the
problem and I don't understand why it's always the third time close
(Cancel) occurs that is causing it to occur.
Basically, I'm stumped. Please help.
Any documentation about CorExitProcess would also help.
native code. The form pop-up correctly and run correctly UNTIL I try to close
the form. The close procedure basically is just a cleanup destructor written
in C++
that works fine the first two times it's used. The third time it appears to
work
ok as well but the base application takes an R6025 trap. Debugging this has
been a nightmare. I do single step in the debugger in the forms code and see
no
problems. I've added code to use _set_purecall_handler() in the wrapper
code that creates the .NET Form object but it never gets called unless I
force it.
When I force it, the base application appears to die in a consistent manner.
The stack trace I get when this occurs is:
msvc71d.dll!_NMSG_Write(rterrnum=25)
msvc71d.dll!_amsg_exit(rterrnum=25)
msvc71d.dll!_purecall()
mscorwrks.dll!CorExitProcess()
1b28a04e()
All of the stack looks ok except the CorExitProcess() function which I can not
get any documentation on or for that matter any related crash info on.
I need to know what is going on so I can fix what I'm doing wrong.
I do have virtual functions in the code but I'm pretty sure that they
aren't being called unless some magic in the constructors are causing
it to happen implicitly, there is no explicit calls in the constructors.
All I do is create the form, then click on my cancel button to cause the
problem and I don't understand why it's always the third time close
(Cancel) occurs that is causing it to occur.
Basically, I'm stumped. Please help.
Any documentation about CorExitProcess would also help.