From: Keith Owens <kaos@sgi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [OT] backtrace
Date: Thu, 03 Oct 2002 19:38:09 +1000 [thread overview]
Message-ID: <7453.1033637889@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Thu, 03 Oct 2002 09:31:06 +0100." <3D9C004A.3080006@corvil.com>
On Thu, 03 Oct 2002 09:31:06 +0100,
Padraig Brady <padraig.brady@corvil.com> wrote:
>Sorry to go off topic but this tip is just too useful IMHO.
>You can do the same in userspace with glibc. Details here:
>http://www.iol.ie/~padraiga/backtrace.c
info libc, /backtrace.
Note that certain compiler optimisations may interfere with
obtaining a valid backtrace. Function inlining causes the inlined
function to not have a stack frame; tail call optimisation
replaces one stack frame with another; frame pointer elimination
will stop `backtrace' from interpreting the stack contents
correctly.
Most architectures compile with -fomit-frame-pointer (except for ARM
where RMK does it differently). Neither gdb not glibc can cope with
kernel code built with -fomit-frame-pointer. See the horrible
heuristics kdb has to apply to get any sort of backtrace on i386.
next prev parent reply other threads:[~2002-10-03 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 9:22 [patch] dump_stack() cleanup, BK-curr Ingo Molnar
2002-10-02 14:59 ` Martin J. Bligh
2002-10-02 16:35 ` Daniel Phillips
2002-10-03 8:31 ` [OT] backtrace Padraig Brady
2002-10-03 9:38 ` Keith Owens [this message]
2002-10-03 10:03 ` Mike Galbraith
2002-10-03 13:40 ` Russell King
2002-10-03 15:46 ` David Mosberger-Tang
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=7453.1033637889@ocs3.intra.ocs.com.au \
--to=kaos@sgi.com \
--cc=linux-kernel@vger.kernel.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).