This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug backtrace/16558] New: GDB Aarch64 signal frame unwinder issue
- From: "teawater at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 12 Feb 2014 01:59:59 +0000
- Subject: [Bug backtrace/16558] New: GDB Aarch64 signal frame unwinder issue
- Auto-submitted: auto-generated
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.