This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug backtrace/14506] New: signal frame should display the signal


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

             Bug #: 14506
           Summary: signal frame should display the signal
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: backtrace
        AssignedTo: unassigned@sourceware.org
        ReportedBy: tromey@redhat.com
    Classification: Unclassified


Currently a backtrace will just print this for a signal delivery:

#3  <signal handler called>

gdb often knows the signal here, so it should display it.

If you look at the backtrace here:
https://bugzilla.redhat.com/show_bug.cgi?id=849588
Direct link:
https://bugzilla.redhat.com/attachment.cgi?id=605630

... you can see a case where the signal is not evident in the bt.
The bt output makes it look like the signal calls quit_force directly.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]