From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-15528-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 28915 invoked by alias); 9 Apr 2014 15:32:40 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Received: (qmail 28888 invoked by uid 48); 9 Apr 2014 15:32:39 -0000
From: "malaperle at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/16812] SIGSEGV running program after using
 dprintf-style call and -dprintf-insert
Date: Wed, 09 Apr 2014 15:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: breakpoints
X-Bugzilla-Version: 7.7
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: malaperle at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-16812-4717-n1X8YBKYdl@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16812-4717@http.sourceware.org/bugzilla/>
References: <bug-16812-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-q2/txt/msg00034.txt.bz2

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.