News:

When registered with our forums, feel free to send a "here I am" post here to differ human beings from SPAM bots.

Main Menu

Bug in debugger plugin

Started by Max, March 29, 2007, 03:46:46 PM

Previous topic - Next topic

Max

I think I am observing a bug in the nightly 3788 (latest) windows xp sp2.

1) open any project (windows winapi exe in my case) compiled for debugging (-g)
2) set a breakpoint in the file foo.c (any source file)
3) start the debugging session
4) when the program stops at the breakpoint close the source window for foo.c
5) reopen the file foo.c
6) the red dot is disappeared but the breakpoint is still there and it is still working

only the red dot is no longer displayed.


Max

Baco

I tried with the nightly build 3989 and with the 1.0RC2.
After reopening the file closed the red dot appears always.
The only thing that disappeared was the yellow triangle indicating the line where execution it was actually stopped.

Biplab

Quote from: Baco on June 07, 2007, 04:37:17 PM
The only thing that disappeared was the yellow triangle indicating the line where execution it was actually stopped.

Fixed in revision 4068. :)
Be a part of the solution, not a part of the problem.

dmoore

I don't know if anyone else encounters this: set a break point, start the program and run to the breakpoint. uncheck the breakpoint by left clicking in the editor pane, run again, the debugger will (almost always?) stop on the unchecked bookmark.

Also a missing feature: add selection to watch (currently you can only add a word to a watch but often you want to see myobject->member)
Python plugins: [url="https://github.com/spillz/codeblocks-python"]https://github.com/spillz/codeblocks-python[/url]
Code::Blocks Daily Builds -- Ubuntu PPA: [url="https://launchpad.net/~damien-moore/+archive/codeblocks"]https://launchpad.net/~damien-moore/+archive/codeblocks[/url]

dmoore

I'll follow up on this with a more complete report later...

PS: what version of gdb is officially supported?
Python plugins: [url="https://github.com/spillz/codeblocks-python"]https://github.com/spillz/codeblocks-python[/url]
Code::Blocks Daily Builds -- Ubuntu PPA: [url="https://launchpad.net/~damien-moore/+archive/codeblocks"]https://launchpad.net/~damien-moore/+archive/codeblocks[/url]

Pecan

Quote from: dmoore on June 16, 2007, 02:44:13 PM
I don't know if anyone else encounters this: set a break point, start the program and run to the breakpoint. uncheck the breakpoint by left clicking in the editor pane, run again, the debugger will (almost always?) stop on the unchecked bookmark.
...

Yes, I encounter this problem frequently.

I've learned to set more than one breakpoint, and to set the first breakpoint as a dummy in a place that won't get hit.

Then I forget about it, and all works well.

byo

Quote from: dmoore on June 16, 2007, 02:44:13 PM
I don't know if anyone else encounters this: set a break point, start the program and run to the breakpoint. uncheck the breakpoint by left clicking in the editor pane, run again, the debugger will (almost always?) stop on the unchecked bookmark.

Also a missing feature: add selection to watch (currently you can only add a word to a watch but often you want to see myobject->member)

I also see this bug frequently. It always occur when I try to debug wxSmith plugin. I guess that this could be related to main application used to run/debug project. wxSmith uses codeblocks.exe so maybe it is path-related problem.

Regards
   BYO

hangl

another problem:sometimes ,set a break point ,but debugger never stop on where I set the point.  definitely, the code that the break point was seted will run and compiling with  debugger option.