public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "teawater at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug backtrace/16558] New: GDB Aarch64 signal frame unwinder issue Date: Wed, 12 Feb 2014 02:00:00 -0000 [thread overview] Message-ID: <bug-16558-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16558 Bug ID: 16558 Summary: GDB Aarch64 signal frame unwinder issue Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: backtrace Assignee: unassigned at sourceware dot org Reporter: teawater at gmail dot com The signal frame unwinder in GDB on Aarch64 seems to have troubles, e.g. the frame where the signal was triggered is skipped. Seen in: (gdb) PASS: gdb.base/relativedebug.exp: continue bt #0 0x0000007fb7e1d5dc in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x0000007fb7e20aac in __GI_abort () at abort.c:89 #2 0x0000000000400850 in handler (signo=14) at /scratch/macro/aarch64-linux-wrs/src/gdb-7.6-yocto/gdb/testsuite/gdb.base/relativedebug.c:25 #3 <signal handler called> #4 main () at /scratch/macro/aarch64-linux-wrs/src/gdb-7.6-yocto/gdb/testsuite/gdb.base/relativedebug.c:33 FAIL: gdb.base/relativedebug.exp: pause found in backtrace where pause's frame is missing between #3 and #4 and also in other test cases where also other frame data is incorrect. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-02-12 2:00 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-12 2:00 teawater at gmail dot com [this message] 2014-02-12 2:00 ` [Bug backtrace/16558] " teawater at gmail dot com 2014-02-12 2:25 ` teawater at gmail dot com 2014-03-06 8:51 ` teawater at gmail dot com 2014-05-20 5:21 ` cvs-commit at gcc dot gnu.org 2014-05-21 0:54 ` teawater at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-16558-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).