[Bug breakpoints/15317] New: Differentiate between SIGTRAP and breakpoint

[Bug breakpoints/15317] New: Differentiate between SIGTRAP and breakpoint

[byron at hawkinssoftware dot net]

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.

[Bug breakpoints/15317] Differentiate between SIGTRAP and breakpoint

[jan.kratochvil at redhat dot com]

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

Jan Kratochvil <jan.kratochvil at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |jan.kratochvil at redhat
                   |                            |dot com

--- Comment #1 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2013-03-31 20:29:43 UTC ---
"handle SIGTRAP nostop noprint" works for me with kernel-3.8.3-203.fc18.x86_64.
It starts ignoring "kill -TRAP child" but "break func"+"continue" still
correctly breaks on "func".

Maybe there is something more specific on "DynamoRIO".

-- 
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.

[Bug breakpoints/15317] Differentiate between SIGTRAP and breakpoint

[sergiodj at redhat dot com]

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

Sergio Durigan Junior <sergiodj at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
                 CC|                            |sergiodj at redhat dot com
         Resolution|---                         |OBSOLETE

--- Comment #2 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
Closing as OBSOLETE due to inactivity.  Feel free to reopen if still valid.

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