aboutsummaryrefslogtreecommitdiff
path: root/configure
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2013-01-22 20:22:39 +0000
committerPedro Alves <palves@redhat.com>2013-01-22 20:22:39 +0000
commit0928e93dfdc0fac8849999962e2ef69cf638fd9a (patch)
treeecfc8aecd2e924e36d43ac4d63822b1184ae5b31 /configure
parent9c97429fb1870f53e69556e967d01ce01116b35e (diff)
downloadfsf-binutils-gdb-0928e93dfdc0fac8849999962e2ef69cf638fd9a.zip
fsf-binutils-gdb-0928e93dfdc0fac8849999962e2ef69cf638fd9a.tar.gz
fsf-binutils-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 'configure')
0 files changed, 0 insertions, 0 deletions