Re: Application "Nuked"


"Kristofer Skaug" <nospam@xxxxxxxxx> wrote

> > Stack overflow?

> Read that somewhere too, now just created a very simple
< test app for this, and in a main thread you get stack overflow
> exception handled by the default app exception handler.

I have been there and seen that, *but* on the next processing
cycle of my app after the overflow, the "poof" happened.
(The stack overflow was likely my own programming error.)

There was a *good* discussion of this problem and the use
of madExcept and EurekaLog just a few weeks ago in one
of the Borland forums.

Regards, JohnH
.

Relevant Pages

  • Re: EnableThemingInScope not being removed
    ... Stack overflow has nothing to do with GC, ... DoEvents to drive the app. ... > API and that I shouldn't be using it for this purpose. ... >> holding them. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: catching Runtime Stack Overflow Exception
    ... appdomain should isolate the hosting application from the catastrophic ... the app ... domain should be allowed to crash and the hosting application should simply ... >> during stack overflow, finally blocks won't fire because there is no ...
    (microsoft.public.dotnet.framework)
  • Re: Application "Nuked"
    ... now just created a very simple test app for ... > default app exception handler. ... Put the stack overflow in a button and press it twice. ...
    (borland.public.delphi.non-technical)
  • Re: Application "Nuked"
    ... Should be easy to create a test to verify it. ... Read that somewhere too, now just created a very simple test app for this, ... in a main thread you get stack overflow exception handled by the default app ... exception handler. ...
    (borland.public.delphi.non-technical)
  • Re: Application "Nuked"
    ... > Put the stack overflow in a button and press it twice. ... The app should ... > vanish on the second try. ...
    (borland.public.delphi.non-technical)