aboutsummaryrefslogtreecommitdiff
path: root/bfd
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2014-06-02 22:27:33 +0100
committerPedro Alves <palves@redhat.com>2014-06-02 23:29:13 +0100
commit41fac0cf495b84994046901e3293d54e8eef3534 (patch)
tree4820fee91254e97a26464c16961e7ec42467e9f0 /bfd
parentcd1608cc4ed6e657deb405283011a6c2a795fb80 (diff)
downloadgdb-41fac0cf495b84994046901e3293d54e8eef3534.zip
gdb-41fac0cf495b84994046901e3293d54e8eef3534.tar.gz
gdb-41fac0cf495b84994046901e3293d54e8eef3534.tar.bz2
Installing a breakpoint on top of a dprintf makes GDB lose control.
While the full fix for PR 15180 isn't in, it's best if we at least make sure that GDB doesn't lose control when a breakpoint is set at the same address as a dprintf. gdb/ 2014-06-02 Pedro Alves <palves@redhat.com> * breakpoint.c (build_target_command_list): Don't build a command list if we have any duplicate location that isn't a dprintf. gdb/testsuite/ 2014-06-02 Pedro Alves <palves@redhat.com> * gdb.base/dprintf-bp-same-addr.c: New file. * gdb.base/dprintf-bp-same-addr.exp: New file.
Diffstat (limited to 'bfd')
0 files changed, 0 insertions, 0 deletions