Re: Mixed assembly crashes on exit

Jim,

Try to enable mixed mode debugging (in the project that you use to start debugging -
probably, that's the main .exe's project):
(Project properties | Configuration Properties | Debugging | Debugger Type -
set to "Mixed" (but not "Auto")
It should allow to set breakpoints in all kinds of code.

The second time, what exception was reported? Was it also stack overflow,
or another one? Is there always the same exception reported after the crash,
or are there different exceptions?

What does Debug Output window contain after a crash? Are there messages
about some other (first chance) exceptions?

Try to reproduce the problem several times in a row. Will it always occur in the same place?
With the same call stack and exception type? If everything is the same, is it still the same
if you let the app run for a while, then exit?

(This all may sound like waste of time, but really it should help to see if the problem
is random or not; if it always occurs in the same way, probably there is one place
where the corruption / misconfiguration occurs, and we will try to find it;
if it occurs truly randomly, we will have to invent something else to spot it)

Oleg




.

Relevant Pages

  • Re: Gdi+ bug report
    ... exception which when unhandled triggers the Access Violation. ... debugger and see if there is a stack overflow exception which is happening ... > but could not get the crash to occur there", ... >> I attempted to isolate it by producing a small standalone app, ...
    (microsoft.public.win32.programmer.gdi)
  • Re: Paged Pool memory
    ... When the exception is translated i can see that the exception code is ... This can be a common problem(low resources). ... The problem for crash is stack overflow and i trying to find the reason for ...
    (microsoft.public.win32.programmer.kernel)
  • Re: SetUnhandledExceptionFilter
    ... The only way to prevent at all cost a crash in the applicaiton ... Looking at a full dump of Word.exe and/or LotusNotes is the only way ... A bad heap metadata will cause an access violation, ... normally dismissed in some wide exception handler) ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Event ID 7031 Exchange 2003
    ... I could not find any exceptions in the crashdump file. ... It seems like the information store crash is "silent" with no other error ... What is the process that had the exception. ...
    (microsoft.public.exchange2000.information.store)
  • Re: Standby-Sleep Problem
    ... If your driver does not explicitly show up in the crash dump, then it does not mean that the crash is not your driver's fault. ... If you cannot attach a debugger, then you will not be successful in developing your driver. ... Break instruction exception - code 80000003 ...
    (microsoft.public.development.device.drivers)
Loading