[Bug breakpoints/16812] SIGSEGV running program after using dprintf-style call and -dprintf-insert

["malaperle at gmail dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16812

--- Comment #2 from Marc-Andre Laperle <malaperle at gmail dot com> ---
I'm sorry, I have to rectify the steps to reproduce the bug. I had a .gdbinit
file in my home directory that affected the behavior. Here are the correct
steps:

(gdb) 
handle SIGSEGV nostop noprint
&"handle SIGSEGV nostop noprint\n"
~"Signal        Stop\tPrint\tPass to program\tDescription\n"
~"SIGSEGV       No\tNo\tYes\t\tSegmentation fault\n"
^done
(gdb) 
-gdb-set dprintf-style call
^done
(gdb) 
-dprintf-insert test.cpp:13 "hello"
^done,bkpt={number="1",type="dprintf",disp="keep",enabled="y",addr="0x0000000000400861",func="main()",file="test.cpp",fullname="/home/emalape/git/gdb-7.7/install/bin/test.cpp",line="13",thread-groups=["i1"],times="0",script={"call
(void) printf (\"hello\")"},original-location="test.cpp:13"}
(gdb) 
r
&"r\n"
~"Starting program: /home/emalape/git/gdb-7.7/install/bin/test \n"
=thread-group-started,id="i1",pid="28110"
=thread-created,id="1",group-id="i1"
^running
...
=library-loaded,id="/lib/x86_64-linux-gnu/libgcc_s.so.1",target-name="/lib/x86_64-linux-gnu/libgcc_s.so.1",host-name="/lib/x86_64-linux-gnu/libgcc_s.so.1",symbols-loaded="0",thread-group="i1"
=breakpoint-modified,bkpt={number="1",type="dprintf",disp="keep",enabled="y",addr="0x0000000000400861",func="main()",file="test.cpp",fullname="/home/emalape/git/gdb-7.7/install/bin/test.cpp",line="13",thread-groups=["i1"],times="0",script={"call
(void) printf (\\"hello\\")"},original-location="test.cpp:13"}
=breakpoint-modified,bkpt={number="1",type="dprintf",disp="keep",enabled="y",addr="0x0000000000400861",func="main()",file="test.cpp",fullname="/home/emalape/git/gdb-7.7/install/bin/test.cpp",line="13",thread-groups=["i1"],times="1",script={"call
(void) printf (\\"hello\\")"},original-location="test.cpp:13"}
~"\nProgram terminated with signal "
~"SIGSEGV, Segmentation fault.\n"
~"The program no longer exists.\n"
=thread-exited,id="1",group-id="i1"
=thread-group-exited,id="i1"
*stopped
Aborted



If only nostop is used then it works correctly:
handle SIGSEGV nostop

-- 
You are receiving this mail because:
You are on the CC list for the bug.