Re: DebugBreak continue issue

Hi Norbert,

1.

I have tested that in the following code, if no exception handler, and if we
at the same time set a break point to the line return TRUE, then if we click
continue, it will break at the line of return TRUE.

So, I think it conforms to your below comments, if no exception handler,
execution continues, right?


My question is, if there is an exception handler in the caller of the
function, then it is not correct to call return TRUE and the correct
operation should be stack unwind. It depends on how you define continue
execution, continue the next line or continue the stack unwind? Any comments?

Do you have any documents which says continue means continue next line, not
continue the normal operation -- stack unwinding?

Here is what I get when press F1 for the Break-Continue-Ignore dialog,

--------------------
 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.
--------------------

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

[Code]
#include "Windows.h"

int main()
{
    int a;
    int b;
    int c;

    /*__try
    {
    */
        a = 100;
        b = 200;
        c = 300;

        DebugBreak();
        a = 400;
    /*
    }
    __except(GetExceptionCode() == EXCEPTION_BREAKPOINT ?
             EXCEPTION_EXECUTE_HANDLER : EXCEPTION_CONTINUE_SEARCH)
    {
        // No debugger is attached, so return FALSE
        // and continue.
        return FALSE;
    }
    */

    return TRUE; // if set break point here, and select continue, will break
here.
}
[/Code]

2.


Debugger you mean JIT debugger?

regards,
George