Questions for Debug in C::B

[lehe]

Hi,
I am using  C::B svn 5532. But the following two debugging problems have also been existing in older versions:

1. If a breakpoint is set at some loop and the execution resumes from there, the loop execution will be very slow and seems to run forever, which is abnormal since the execution of the loop will be very fast if without a breakpoint there. In such case, I found a *trick* to accelerate it by setting another breakpoints a few lines ahead, which will  make the program go over the loop and stop at that breakpoint added ahead.  However this will give "Program received signal SIGINT, Interrupt" information in Debug window. So I doubt if this trick actually works at all.

2. When my program stops at a breakpoint and I want to switch to another stack, clicking on the stack in the stack window doesn't work since the variables of that stack are still not defined in the current scope. The only way I found can work is to type gdb command in Debug->Send user command to debugger.

Are these really problems of C::B or am I missing something? Please comment.  Thank you very much!

[TDragon]

2. When my program stops at a breakpoint and I want to switch to another stack, clicking on the stack in the stack window doesn't work since the variables of that stack are still not defined in the current scope. The only way I found can work is to type gdb command in Debug->Send user command to debugger.

Double-click the line to switch to that stack frame.

[lehe]

Thanks!
I just found right-click on the stack line will pop out an option "Switch to this frame" which works, but double-click doesn't work.

Does someone know about my first problem?  Does the "Program received signal SIGINT, Interrupt" info mean that the loop is not properly executed?