From: Detlev Zundel <dzu@denx.de>
To: linuxppc-dev@ozlabs.org
Subject: Re: Signal backtrace function
Date: Mon, 14 Apr 2008 18:09:00 +0200 [thread overview]
Message-ID: <m2skxoo1ur.fsf@ohwell.denx.de> (raw)
In-Reply-To: 1207764980.5826.77.camel@gentoo-jocke.transmode.se
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?
Thanks
Detlev
--
The management question ... is not _whether_ to build a pilot system
and throw it away. You _will_ do that. The only question is whether to
plan in advance to build a throwaway, or to promise to deliver the
throwaway to customers. - Fred Brooks, "The Mythical Man Month"
--
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
next prev parent reply other threads:[~2008-04-14 16:09 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 [this message]
2008-04-14 16:20 ` Joakim Tjernlund
2008-04-15 15:50 ` Detlev Zundel
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=m2skxoo1ur.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--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).