This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/15317] New: Differentiate between SIGTRAP and breakpoint
- From: "byron at hawkinssoftware dot net" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 27 Mar 2013 20:30:17 +0000
- Subject: [Bug breakpoints/15317] New: Differentiate between SIGTRAP and breakpoint
- Auto-submitted: auto-generated
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.