aboutsummaryrefslogtreecommitdiff
path: root/gdb/event-top.c
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2013-01-22 20:17:10 +0000
committerPedro Alves <palves@redhat.com>2013-01-22 20:17:10 +0000
commitbd00c69423eff0d06f1632cfb50ccb5d8ab58151 (patch)
tree6632e60949d293c989df835c171e4760d68c8b1d /gdb/event-top.c
parent187d10dd19b822ba6e5470f1bd67fc94f5b48a86 (diff)
downloadgdb-bd00c69423eff0d06f1632cfb50ccb5d8ab58151.zip
gdb-bd00c69423eff0d06f1632cfb50ccb5d8ab58151.tar.gz
gdb-bd00c69423eff0d06f1632cfb50ccb5d8ab58151.tar.bz2
With some changes to how software single-step (SSS) breakpoints are
handled, one of those being to place SSS breakpoints on the breakpoint chain as all other breakpoints, annota1.exp times out with lots and lots of breakpoint-invalid and frame-changed annotations. All those extra annotations are actually unnecessary. For one, SSS breakpoints are internal breakpoints, so the frontend shouldn't care if they were added, removed or changed. Then, there's really no point in emitting "breakpoints-invalid" or "frames-invalid" more than once between times the frontend/user can actually issues GDB commands; the frontend will have to wait for the GDB prompt to refresh its state, so emitting those annotations at most once between prompts is enough. Non-stop or async would complicate this, but no frontend will be using annotations in those modes (one of goes of emacs switching to MI was non-stop mode support, AFAIK). The previous patch reveals there has been an intention in the past to suppress multiple breakpoints-invalid annotations caused by ignore count changes. As the previous patch shows, that's always been broken, but in any case, this patch actually makes it work. The next patch will remove several annotation-specific calls in breakpoint.c in favor of always using the breakpoint modified & friends observers, and that causes yet more of these annotations, because several calls to the corresponding annotate_* functions in breakpoint.c are missing, particularly in newer code. So all in all, here's a simple mechanism that avoids sending the same annotation to the frontend more than once until gdb is ready to accept further commands. Tested on x86_64 Fedora 17. 2013-01-22 Pedro Alves <palves@redhat.com> * annotate.c: Include "inferior.h". (frames_invalid_emitted) (breakpoints_invalid_emitted): New globals. (async_background_execution_p): New function. (annotate_breakpoints_changed, annotate_frames_invalid): Skip emitting the annotation if it has already been emitted. (annotate_display_prompt): New function. * annotate.h (annotate_display_prompt): New declaration. * event-top.c: Include annotate.h. (display_gdb_prompt): Call annotate_display_prompt.
Diffstat (limited to 'gdb/event-top.c')
-rw-r--r--gdb/event-top.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/gdb/event-top.c b/gdb/event-top.c
index 1b75bbd..9f415b2 100644
--- a/gdb/event-top.c
+++ b/gdb/event-top.c
@@ -35,6 +35,7 @@
#include "observer.h"
#include "continuations.h"
#include "gdbcmd.h" /* for dont_repeat() */
+#include "annotate.h"
/* readline include files. */
#include "readline/readline.h"
@@ -231,6 +232,8 @@ display_gdb_prompt (char *new_prompt)
char *actual_gdb_prompt = NULL;
struct cleanup *old_chain;
+ annotate_display_prompt ();
+
/* Reset the nesting depth used when trace-commands is set. */
reset_command_nest_depth ();