summaryrefslogtreecommitdiff
path: root/gdb/jv-valprint.c
diff options
context:
space:
mode:
authorJoel Brobecker <brobecker@gnat.com>2012-08-16 23:54:36 +0000
committerJoel Brobecker <brobecker@gnat.com>2012-08-16 23:54:36 +0000
commit7bdaa230a7fc333f81a0622d330ad2c6b010a08d (patch)
tree30006e2205505c368b1164e0bd2df59014b2a4ea /gdb/jv-valprint.c
parent217968566e210aefa576734b8859a4177bd3dd53 (diff)
downloadgdb-7bdaa230a7fc333f81a0622d330ad2c6b010a08d.tar.gz
inf_ttrace_follow_fork: detach_breakpoints called twice for child.
When debugging a program that forks with follow-fork set to follow the parent, we end up calling detach_breakpoints for the child twice. On ia64-hpux, this leads to a warning when trying to remove the breakpoints the second time around, because the ia64 code detects that the address does not point to a breakpoint instruction. gdb/ChangeLog: * inf-ttrace.c (inf_ttrace_follow_fork): When following the parent, only call detach_breakpoints if tts.tts_event == TTEVT_VFORK.
Diffstat (limited to 'gdb/jv-valprint.c')
0 files changed, 0 insertions, 0 deletions