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] SPARC: can't compute CFA for this frame
Date: Wed, 27 Nov 2013 13:09:00 -0000	[thread overview]
Message-ID: <bug-16215-4717-CPRtSmnfoi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16215-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16215

--- Comment #1 from Sebastian Huber <sebastian.huber@embedded-brains.de> ---
Created attachment 7308
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7308&action=edit
Workaround patch for GCC

This patch for GCC forces the old debug format.  With it I don't have the
backtrace problems:

(gdb) where
#0  console_write (major=0, minor=0, arg=0x400426f0) at
/home/sh/rtems-4.11/c/src/lib/libbsp/sparc/leon3/console/console.c:452
#1  0x4002a7f0 in rtems_io_write (major=0, minor=0, argument=0x400426f0) at
/home/sh/rtems-4.11/c/src/../../cpukit/sapi/src/iowrite.c:37
#2  0x40029124 in rtems_deviceio_write (iop=0x4004b150, buf=0x40039fe8,
nbyte=25, major=0, minor=0) at
/home/sh/rtems-4.11/c/src/../../cpukit/libcsupport/src/sup_fs_deviceio.c:108
#3  0x40028a3c in device_write (iop=0x4004b150, buffer=0x40039fe8, count=25) at
/home/sh/rtems-4.11/c/src/../../cpukit/libfs/src/imfs/deviceio.c:90
#4  0x40038330 in write (fd=2, buffer=0x40039fe8, count=25) at
/home/sh/rtems-4.11/c/src/../../cpukit/libcsupport/src/write.c:48
#5  0x40037e74 in _write_r (ptr=0x40042c60, fd=2, buf=0x40039fe8, nbytes=25) at
/home/sh/rtems-4.11/c/src/../../cpukit/libcsupport/src/write_r.c:41
#6  0x40033878 in __sfvwrite_r (ptr=0x40042c60, fp=0x40042e98, uio=0x400429d4)
at /home/sh/archive/gcc-git/newlib/libc/stdio/fvwrite.c:99
#7  0x4002dd1c in __sprint_r (ptr=0x40042c60, fp=0x40042e98, uio=0x400429d4) at
/home/sh/archive/gcc-git/newlib/libc/stdio/vfprintf.c:437
#8  0x4002e904 in _vfiprintf_r (data=0x40042c60, fp=<optimized out>,
fmt0=<optimized out>, ap=<optimized out>) at
/home/sh/archive/gcc-git/newlib/libc/stdio/vfprintf.c:1776
#9  0x4002c214 in fiprintf (fp=0x40042e98, fmt=0x40039fe0 "%s\n") at
/home/sh/archive/gcc-git/newlib/libc/stdio/fiprintf.c:50
#10 0x40001420 in Init (argument=1073991032) at
/home/sh/rtems-4.11/c/src/../../testsuites/samples/ticker/init.c:31
#11 0x4002b688 in _Thread_Handler () at
/home/sh/rtems-4.11/c/src/../../cpukit/score/src/threadhandler.c:188
#12 0x4002b5b4 in _Thread_Handler () at
/home/sh/rtems-4.11/c/src/../../cpukit/score/src/threadhandler.c:93

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  reply	other threads:[~2013-11-27 13:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25  8:10 [Bug backtrace/16215] New: " sebastian.huber@embedded-brains.de
2013-11-27 13:09 ` sebastian.huber@embedded-brains.de [this message]
2013-11-27 16:10 ` [Bug backtrace/16215] " 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-CPRtSmnfoi@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).