[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 118327] break point is not displayed if set manually
From:       Thomas McGuire <Thomas.McGuire () gmx ! net>
Date:       2007-04-11 19:02:38
Message-ID: 20070411190238.13326.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=118327         
Thomas.McGuire gmx net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Thomas.McGuire gmx net



------- Additional Comments From Thomas.McGuire gmx net  2007-04-11 21:02 -------
I just ran into this problem as well, with another aspect:

When the breakpoint is hit, it can not be disabled.
To reproduce.
0. Delete all breakpoints
1. Add one breakpoint somewhere so that GDB will stop, let's say main.cpp:42
2. Run the debugger. It will hit the BP in line 42.
3. Use the GDB command window to manually add a breakpoint somewhere later, for \
example main.cpp:46. You the -break-insert command for this, which can mostly be \
copied&pasted from the GDB command history (except line number of course). 4. The \
breakpoint is added, but the editor does not display it. BUG. 5. Continue execution. \
The breakpoint in line 46 is hit now. When this happens, the breakpoint is now \
displayed in the editor. 6. Try to disable the breakpoint by clicking on its icon in \
the editor. GDB will remove the breakpoint, but the editor still displays it. BUG.


[prev in list] [next in list] [prev in thread] [next in thread]