linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: joakim.tjernlund@transmode.se
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Signal backtrace function
Date: Tue, 15 Apr 2008 17:50:45 +0200	[thread overview]
Message-ID: <m2zlrvi0bu.fsf@ohwell.denx.de> (raw)
In-Reply-To: <1208190010.5911.15.camel@gentoo-jocke.transmode.se> (Joakim Tjernlund's message of "Mon, 14 Apr 2008 18:20:09 +0200")

Hi Jocke,

> On Mon, 2008-04-14 at 18:09 +0200, Detlev Zundel wrote:
>> Hi Jocke,
>> 
>> > I made my own backtrace function for printing
>> > a trace from within a signal handler. Maybe it
>> > can be useful for the kernel too? General
>> > comments welcome.
>> 
>> Probably a dumb question, but doesn't backtrace(3) from glibc work
>> architecture independent already?   Why do you need to reimplement it?
>
> Nope, it doesn't give you a good backtrace from within a signal handler.
> On x86 you can use the normal backtrace function with a minor
> workaround, but as ppc doesn't save a FP in leaf functions, that
> workaround does not work well. You can read more about it
> at http://www.linuxjournal.com/article/6391

Thanks for clearing that up.  I wasn't aware of that limitation.

Cheers
  Detlev

-- 
In short: much of our country's [USA] counterterrorism security spending is
not designed to protect us from the terrorists,  but instead to protect our
public officials from criticism when another attack occurs.
                                   -- Bruce Schneier
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de

      reply	other threads:[~2008-04-15 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09 18:16 Signal backtrace function Joakim Tjernlund
2008-04-14 16:09 ` Detlev Zundel
2008-04-14 16:20   ` Joakim Tjernlund
2008-04-15 15:50     ` Detlev Zundel [this message]

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=m2zlrvi0bu.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --cc=joakim.tjernlund@transmode.se \
    --cc=linuxppc-dev@ozlabs.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 NNTP newsgroup(s).