-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.gdbinit breakpoints executed but not shown on GUI #37
Comments
start_gdb() in cgdb.cpp does the following:
tgdb_initialize winds up calling down into a2_initialize(), which does:
When process_commands() gets the TGDB_UPDATE_BREAKPOINTS response, it's before the TGDB_UPDATE_FILE_POSITION response comes in, so we don't have any source information yet and the breakpoint info is dropped. I added a a2_get_current_location() call right before the INFO_BREAKPOINTS call in a2_initialize and it fixed the issue, but I'm not sure it's the best fix. Need to have Bob review this one...
|
#37 Need to request source information before breakpoints. Signed-off-by: Michael Sartain <mikesart@gmail.com> Signed-off-by: Bob Rossi <bob@brasko.net>
Thanks to Michael Sartain, this has been fixed in master. A release will most likely be done in a month or two. |
When you set a breakpoint, the line number on the cgdb GUI turns red.
I set a breakpoint and saved it using "save breakpoints .gdbinit".
.gdbinit
is executed automatically by gdb on startup to restore a previous debugging 'session'. Upon starting cgdb, the gdb prompt at the bottom reports that the breakpoint from .gdbinit has been set, but the GUI is not updated as if no breakpoint is set.Typing any command (or even just an empty one) at the gdb prompt will update the GUI view at the top, reavling the magnificent breakpoint in its red glory.
The text was updated successfully, but these errors were encountered: