A new bug (?) using debugger in the latest nightly

[Max]

Hi, *

Using : Windows XP SP2 and nightly 3703 or the latest 3714

Have a look to the attached picture. Is a debugging session of a piece of stupid code. The problem is:

When I try to setup a watch for an "out of scope" variable the debugger enter in a unbreakable state. All the button related to debugger turn to gray (but not the stop debugger button) and you are not able to stop the debugger. The application window is no longer responding.

In the example I am in the line 174.  Then I try to set a new watch for the  variable pSqlStatement. The variable has the scope defined by the lines 105 to 168 (so I am out of scope for it). In the watches window the message is correct but now the debugger is frozen.


Can you confirm?


Here the image

http://img232.imageshack.us/img232/5916/bugbs2.jpg


Max

[Max]

More....

The bug is present even if I set a watch when I am "in scope".

I see

Setting breakpoints
Debugger name and version: GNU gdb 6.3
Child process PID: 1908
At C:/C/Projects/BookShelf/Search.c:166
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...
Trying to pause the running process...


In the Debugger tab


Max

[hangl]

This problem still exists  in lasest 3721!
And more if I try to  set a watch for a class member  variable, All the button related to debugger also turn to gray(stop debugger button excpet);

[Max]

Thank you hangl tohave confirmed the bug. I eas afraid to be the only one to be affected.

Anyway I tested old nightly to verify when the problem appeared. The version 3656 is OK, newer version not are OK
(well I haven't tested every nightly but 3671 is affected and 3681, 3703, 3714 and 3720 as well)

In the SVN I find at version 3659

3659     /     mandrav     2 weeks     
- Signed/unsigned fix in debugger sources.
* Fixed debugger to be able to stop a program while running (linux).
* Debugger's tooltip evaluation is temporarily disabled.

I think that the problem appeared whit this commit.


Hopefully mandrav will fix this bug, debugging is pretty impossible now.... :-)


Max

[dr snuggles]

I can also confirm this bug. Although it is not a new bug, it has not been fixed afaik. See also this thread for code to reproduce the bug.

Anyway I tested old nightly to verify when the problem appeared. The version 3656 is OK, newer version not are OK

Thanks for pointing this out! Version 3656 (from 1 March 2007) is a lot more stable during debugging .

[mandrav]

Debugger's behavior should be back to normal again (since rev. 3727).

[dr snuggles]

Debugger's behavior should be back to normal again (since rev. 3727).

Thanks!

Although I'm afraid that this build still has the fall through bug. IE: The debugger tries to stop at a breakpoint, but then decides to go on. It's very easy to reproduce the bug with a lot of code, but very hard to reproduce with a few lines. Edit: If I change to GDB 6.3, the debugger does stop at a breakpoint, but stepping into functions (shift f7) shows some weird behaviour. If there are no errors in my code, the weird behaviour is gone.

Is there any build at all which has a completely working debugging functionality in it?

C::B Build: 3730
GDB: 5.2.1
OS: WinXP SP2

 

[Max]

It seems fixed... at least I am no longer observing the issue in the same project used to flag the bug.

Thanks

Massimo