This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
backtrace/1569: Test backtrace through NULL PC sigtramp
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 25 Feb 2004 16:05:24 -0000
- Subject: backtrace/1569: Test backtrace through NULL PC sigtramp
- Reply-to: ac131313 at redhat dot com
>Number: 1569
>Category: backtrace
>Synopsis: Test backtrace through NULL PC sigtramp
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: test-bug
>Submitter-Id: net
>Arrival-Date: Wed Feb 25 16:08:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: 2004-02-25
>Organization:
>Environment:
>Description:
Per the thread:
http://sources.redhat.com/ml/gdb-patches/2004-02/msg00567.html
adding a check for a zero PC isn't valid in the backtrace code. It will stop GDB displaying the full backtrace of a program that caught a call to NULL vis:
sigsegv_handler
<signal trampoline>
(*()) 0
foo (which called "(*()) 0")
main
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: