From: P@draigBrady.com
To: Neil Horman <nhorman@redhat.com>
Cc: Alex Bennee <kernel-hacker@bennee.com>,
"LinuxSH (sf)" <linuxsh-dev@lists.sourceforge.net>,
"Linux-SH (m17n)" <linux-sh@m17n.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] RFC. User space backtrace on segv
Date: Thu, 07 Oct 2004 10:48:01 +0100 [thread overview]
Message-ID: <416510D1.7030406@draigBrady.com> (raw)
In-Reply-To: <41642CBA.7030709@redhat.com>
Neil Horman wrote:
> IIRC, there is already a backtrace function defined for most arches in
> the c library. in execinfo.h there is a family of backtrace functions
> that can unwind the stack fairly well for most arches, and store the
> trace in a post SIGSEGV-safe fashion.
I've some info on this here:
http://www.pixelbeat.org/libs/backtrace.c
Pádraig.
next prev parent reply other threads:[~2004-10-07 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 16:37 [PATCH] RFC. User space backtrace on segv Alex Bennee
2004-10-06 16:39 ` Alex Bennee
2004-10-06 17:17 ` Arnd Bergmann
2004-10-06 17:34 ` Neil Horman
2004-10-07 9:48 ` P [this message]
2004-10-07 10:29 ` RTC (real time clock) question about sh4 7760 Fabio Giovagnini
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=416510D1.7030406@draigBrady.com \
--to=p@draigbrady.com \
--cc=kernel-hacker@bennee.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@m17n.org \
--cc=linuxsh-dev@lists.sourceforge.net \
--cc=nhorman@redhat.com \
/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