Re: DebugBreak continue issue

"George" <George@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:39BC669A-EFAD-4C07-8668-FFE3216ADA07@xxxxxxxxxxxxxxxx
I am trying the continue function triggered by JIT debugger. As mentioned
in
MSDN,

[url]http://msdn2.microsoft.com/zh-cn/library/h22dk1y6(en-us).aspx[/url]

--------------------
Continue
Allows execution to continue, giving the exception handler a chance to
handle the exception. This option is not available for certain types of
exceptions. Continue will allow the application to continue. In a native
application, it will cause the exception to be rethrown. In a managed
application, it will either cause the program to terminate or the
exception
to be handled by a hosting application.
--------------------

Case I: You run under a debugger

The program stops at the breakpoint

Case II: You don't run under the debugger

DebugBreak() raises an exception. _Your_ handler catches it. It does
just about nothing.

The MSDN blurb describes what happens when a breakpoint exception goes
unhandled.

Regards,
Will


.

Relevant Pages

  • Re: How to force the program to continue after unhandled exception detection
    ... Add this handler for form's Load event: ... Run the application without debugger: ... The debugger detects the unhandled exception and stops the program at ... When I set up a ThreadException handler correctly, by subscribing the handler before I call Application.Run, then once the debugger detects the exception and interrupts the program, I can simply continue execution and the program continues running just as it would have had the debugger not been present. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Implementing Exception Handling in a VM
    ... Why does a debugger require to walk the stack twice? ... Delphi) to only pop up the debugger if the exception isn't caught deeper ... MP> EXCEPTION_REGISTRATION structures until it finds a handler for the ...
    (comp.compilers)
  • Re: How to force the program to continue after unhandled exception detection
    ... Run the application without debugger: ... The debugger detects the unhandled exception and stops the program at ... ThreadException event correctly. ... When I set up a ThreadException handler correctly, ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Try Finally...
    ... Now we can protect every more or less specialized action ... an error indication (exception or error code) has to be ... an according exception handler can be inserted into the code. ... resources, as they are related to specific actions. ...
    (comp.lang.pascal.delphi.misc)
  • Re: Strange exception behaviour
    ... I'm left sitting with the debugger pointing to the .ShowDialogcall, ... and showing an exception that obviously happened in some event handler ... As Matt said, this has to do with how .NET is handling calls to the ...
    (microsoft.public.dotnet.framework.windowsforms)
Loading