From: Russell King <rmk@arm.linux.org.uk>
To: Mike Galbraith <efault@gmx.de>
Cc: Keith Owens <kaos@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: [OT] backtrace
Date: Thu, 3 Oct 2002 14:40:59 +0100 [thread overview]
Message-ID: <20021003144058.D2304@flint.arm.linux.org.uk> (raw)
In-Reply-To: <5.1.0.14.2.20021003114625.00b7ea20@pop.gmx.net>; from efault@gmx.de on Thu, Oct 03, 2002 at 12:03:27PM +0200
On Thu, Oct 03, 2002 at 12:03:27PM +0200, Mike Galbraith wrote:
> At 07:38 PM 10/3/2002 +1000, Keith Owens wrote:
> >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.
>
> IIRC, r~ once mentioned that it was going to get worse. He also mentioned
> dwarf2 (sp) as a possible solution. Did you ever look into that?
There was the offer by someone to supply some code, which as per usual
came to nothing.
Therefore its just a bad rumour as far as I'm concerned. I can't do
everything, my days are full enough as it is.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-10-03 13:35 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
2002-10-03 10:03 ` Mike Galbraith
2002-10-03 13:40 ` Russell King [this message]
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=20021003144058.D2304@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=efault@gmx.de \
--cc=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).