From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-13391-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 2702 invoked by alias); 27 Mar 2013 20:30:18 -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 2678 invoked by uid 48); 27 Mar 2013 20:30:17 -0000
From: "byron at hawkinssoftware dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/15317] New: Differentiate between SIGTRAP and
 breakpoint
Date: Wed, 27 Mar 2013 20:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: breakpoints
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: byron at hawkinssoftware dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-15317-4717@http.sourceware.org/bugzilla/>
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
X-SW-Source: 2013-q1/txt/msg00539.txt.bz2

http://sourceware.org/bugzilla/show_bug.cgi?id=15317

             Bug #: 15317
           Summary: Differentiate between SIGTRAP and breakpoint
           Product: gdb
           Version: 7.4
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: breakpoints
        AssignedTo: unassigned@sourceware.org
        ReportedBy: byron@hawkinssoftware.net
    Classification: Unclassified


When I debug programs under DynamoRIO, gdb often stops with a message about a
SIGTRAP that is not a breakpoint. When there are thousands of these stoppages,
debugging becomes impossible. The command "handle SIGTRAP nostop noprint" is
not a viable option, because then the breakpoints are skipped. 

It is clear that gdb knows for every SIGTRAP whether it corresponds to a
breakpoint, because the output is consistently different: at a breakpoint, a
message about a breakpoint appears, but at any other SIGTRAP, nothing about a
breakpoint is printed. So I need another option for the "handle SIGTRAP"
command, which applies only to signals that are not breakpoints. Given the
current behavior of gdb, this feature is certainly possible.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.