public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sebastian.huber@embedded-brains.de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/16215] New: SPARC: can't compute CFA for this frame
Date: Mon, 25 Nov 2013 08:10:00 -0000 [thread overview]
Message-ID: <bug-16215-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16215
Bug ID: 16215
Summary: SPARC: can't compute CFA for this frame
Product: gdb
Version: 7.6
Status: NEW
Severity: normal
Priority: P2
Component: backtrace
Assignee: unassigned at sourceware dot org
Reporter: sebastian.huber@embedded-brains.de
Created attachment 7304
--> https://sourceware.org/bugzilla/attachment.cgi?id=7304&action=edit
Sample ELF file
I use Binutils 2.23.91.20131125, GCC 4.8.3 20131119, and GDB 7.6.1. On SPARC I
don't get proper backtraces since GCC 4.8:
Breakpoint 4, console_write (major=<error reading variable: can't compute CFA
for this frame>, minor=<error reading variable: can't compute CFA for this
frame>, arg=<error reading variable: can't compute CFA for this frame>) at
/home/sh/rtems-4.11/c/src/lib/libbsp/sparc/leon3/console/console.c:484
484 return rtems_termios_write(arg);
(gdb) where
#0 console_write (major=<error reading variable: can't compute CFA for this
frame>, minor=<error reading variable: can't compute CFA for this frame>,
arg=<error reading variable: can't compute CFA for this frame>) at
/home/sh/rtems-4.11/c/src/lib/libbsp/sparc/leon3/console/console.c:484
#1 0x40028694 in rtems_io_write (major=<error reading variable: can't compute
CFA for this frame>, minor=<error reading variable: can't compute CFA for this
frame>, argument=<error reading variable: can't compute CFA for this frame>) at
/home/sh/rtems-4.11/c/src/../../cpukit/sapi/src/iowrite.c:37
#2 0x40026e38 in rtems_deviceio_write (iop=<error reading variable: can't
compute CFA for this frame>, buf=<error reading variable: can't compute CFA for
this frame>, nbyte=<error reading variable: can't compute CFA for this frame>,
major=<error reading variable: can't compute CFA for this frame>, minor=<error
reading variable: can't compute CFA for this frame>) at
/home/sh/rtems-4.11/c/src/../../cpukit/libcsupport/src/sup_fs_deviceio.c:108
#3 0x40026754 in device_write (iop=<error reading variable: can't compute CFA
for this frame>, buffer=<error reading variable: can't compute CFA for this
frame>, count=<error reading variable: can't compute CFA for this frame>) at
/home/sh/rtems-4.11/c/src/../../cpukit/libfs/src/imfs/deviceio.c:90
#4 0x40036a20 in write (fd=<error reading variable: can't compute CFA for this
frame>, buffer=<error reading variable: can't compute CFA for this frame>,
count=<error reading variable: can't compute CFA for this frame>) at
/home/sh/rtems-4.11/c/src/../../cpukit/libcsupport/src/write.c:48
#5 0x400365d8 in _write_r (ptr=<error reading variable: can't compute CFA for
this frame>, fd=<error reading variable: can't compute CFA for this frame>,
buf=<error reading variable: can't compute CFA for this frame>, nbytes=<error
reading variable: can't compute CFA for this frame>) at
/home/sh/rtems-4.11/c/src/../../cpukit/libcsupport/src/write_r.c:41
#6 0x40031414 in __sfvwrite_r (ptr=ptr@entry=0x40041020,
fp=fp@entry=0x40041258, uio=uio@entry=0x40040d94) at
/home/sh/archive/gcc-git/newlib/libc/stdio/fvwrite.c:99
#7 0x4002b8c0 in __sprint_r (ptr=ptr@entry=0x40041020, fp=fp@entry=0x40041258,
uio=uio@entry=0x40040d94) at
/home/sh/archive/gcc-git/newlib/libc/stdio/vfprintf.c:437
#8 0x4002c4a4 in __sprint_r (uio=0x40040d94, fp=0x40041258, ptr=0x40041020) at
/home/sh/archive/gcc-git/newlib/libc/stdio/vfprintf.c:1776
#9 _vfiprintf_r (data=0x40041020, fp=fp@entry=0x40041258,
fmt0=fmt0@entry=0x40038528 "%s\n", ap=<optimized out>) at
/home/sh/archive/gcc-git/newlib/libc/stdio/vfprintf.c:1776
#10 0x40029f6c in fiprintf (fp=0x40041258, fmt=0x40038528 "%s\n") at
/home/sh/archive/gcc-git/newlib/libc/stdio/fiprintf.c:50
#11 0x40001354 in Init (argument=<error reading variable: can't compute CFA for
this frame>) at
/home/sh/rtems-4.11/c/src/../../testsuites/samples/ticker/init.c:31
#12 0x400293f0 in _Thread_Handler () at
/home/sh/rtems-4.11/c/src/../../cpukit/score/src/threadhandler.c:188
#13 0x40029348 in _Thread_Handler () at
/home/sh/rtems-4.11/c/src/../../cpukit/score/src/threadhandler.c:93
You can run the ELF file with Qemu:
qemu-system-sparc -s -S -nographic -M leon3_generic -m 64M -kernel ticker.exe
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2013-11-25 8:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 8:10 sebastian.huber@embedded-brains.de [this message]
2013-11-27 13:09 ` [Bug backtrace/16215] " sebastian.huber@embedded-brains.de
2013-11-27 16:10 ` tromey at redhat dot com
2013-11-28 0:25 ` mkhoory at eiast dot ae
2014-03-24 18:21 ` sebastian.huber@embedded-brains.de
2014-09-24 11:39 ` sebastian.huber@embedded-brains.de
2014-12-13 13:27 ` cvs-commit at gcc dot gnu.org
2014-12-13 15:26 ` cvs-commit at gcc dot gnu.org
2014-12-25 0:46 ` cvs-commit at gcc dot gnu.org
2014-12-31 7:22 ` cvs-commit at gcc dot gnu.org
2015-01-15 11:40 ` brobecker at gnat 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-16215-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: link
Be 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).