[winedbg] Don't ever pass a NONCONTINUABLE exception

Alexandre Julliard julliard at winehq.org
Mon Aug 22 12:37:00 CDT 2005

Glenn Wurster <gwurster at scs.carleton.ca> writes:

> In short, because we're never going to be able to continue, so there's
> no point on trying to pass because that's going to fail.

Not really, if the app handles the exception there's no reason it
would fail. Not passing the exception will break things like

> In long, because I've got another patch in the pipeline (it needs some
> tweaking) that moves the calling of the debugger into the signal
> handler.  It allows the debugger to catch exceptions that would
> previously have resulted in a total crash (non-continuable
> exceptions), and it more accurately reflects how the Windows debugger
> is called.  Using a debugger will also no longer modify program memory
> as it does currently.  In all, it should allow the debugger to work in
> more circumstances than it currently does.

Well, I'll wait to see the patch, but I doubt we want to do that. The
current way is pretty much identical to what Windows does, and it
sounds like your way isn't.

Alexandre Julliard
julliard at winehq.org

More information about the wine-devel mailing list