diff options
| author | Pedro Alves <palves@redhat.com> | 2013-01-22 20:22:39 +0000 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2013-01-22 20:22:39 +0000 |
| commit | 0928e93dfdc0fac8849999962e2ef69cf638fd9a (patch) | |
| tree | ecfc8aecd2e924e36d43ac4d63822b1184ae5b31 /gdb/annotate.c | |
| parent | 9c97429fb1870f53e69556e967d01ce01116b35e (diff) | |
| download | gdb-0928e93dfdc0fac8849999962e2ef69cf638fd9a.zip gdb-0928e93dfdc0fac8849999962e2ef69cf638fd9a.tar.gz gdb-0928e93dfdc0fac8849999962e2ef69cf638fd9a.tar.bz2 | |
If a breakpoint is not user visible, then there's no point in
bothering the frontend about it... This is the exact same check MI
does.
I also smoke tested Emacs 23 in gud-gdb mode, both annotations=2
and annotations=3. I didn't notice anything break.
gdb/
2013-01-22 Pedro Alves <palves@redhat.com>
* annotate.c (breakpoint_changed): Skip if breakpoint is not
user-visible.
gdb/testsuite/
2013-01-22 Pedro Alves <palves@redhat.com>
* gdb.base/annota1.exp (signal sent): No longer expect
breakpoints-invalid.
* gdb.cp/annota2.exp (continue until exit)
(watch triggered on a.x): Ditto.
Diffstat (limited to 'gdb/annotate.c')
| -rw-r--r-- | gdb/annotate.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/gdb/annotate.c b/gdb/annotate.c index d82daa2..ccba5fe 100644 --- a/gdb/annotate.c +++ b/gdb/annotate.c @@ -575,6 +575,9 @@ annotate_display_prompt (void) static void breakpoint_changed (struct breakpoint *b) { + if (b->number <= 0) + return; + annotate_breakpoints_invalid (); } |