From: Catalin Marinas <catalin.marinas@arm.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Hui Zhu <teawater@gmail.com>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
Yao Qi <yao@codesourcery.com>, Eric Miao <eric.y.miao@gmail.com>,
linux-arm-kernel@lists.infradead.org, gdb@sourceware.org
Subject: Re: Problem with GDB when debugging IRQ handlers
Date: Tue, 28 Jun 2011 13:22:00 -0000 [thread overview]
Message-ID: <20110628132407.GB7255@1n450.cable.virginmedia.net> (raw)
In-Reply-To: <20110628120928.GD21898@n2100.arm.linux.org.uk>
On Tue, Jun 28, 2011 at 01:09:28PM +0100, Russell King - ARM Linux wrote:
> On Tue, Jun 28, 2011 at 08:06:27PM +0800, Hui Zhu wrote:
> > If this kernel didn't open FRAME_POINTER, what will happen?
>
> I can't answer that question directly, as I don't use a toolchain new
> enough to generate proper unwind information.
>
> However, I haven't seen any problems being reported on the list with
> bad/broken backtraces from the kernel, so my _assumption_ is that the
> kernel is fine with its own debug info.
I tested this when contributing the unwinding support and it was ok. The
reason is that the svc_entry macro in entry-armv.S adds some annotations
line .fnstart and .save that generate the correct unwinding bytecodes
(but as I said, that's different from the dwarf information which
probably needs different annotations).
--
Catalin
prev parent reply other threads:[~2011-06-28 13:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110627125306.GA30646@doriath.ww600.siemens.net>
[not found] ` <20110627132735.GE16103@n2100.arm.linux.org.uk>
2011-06-27 14:04 ` Dmitry Eremin-Solenikov
2011-06-27 14:12 ` Hui Zhu
2011-06-27 14:59 ` Yao Qi
2011-06-28 10:40 ` Russell King - ARM Linux
2011-06-28 12:06 ` Dmitry Eremin-Solenikov
2011-06-28 12:14 ` Russell King - ARM Linux
2011-06-28 14:19 ` Catalin Marinas
2011-06-28 14:29 ` Catalin Marinas
2011-06-28 14:38 ` Russell King - ARM Linux
2011-06-28 14:42 ` Catalin Marinas
2011-06-28 14:44 ` Dmitry Eremin-Solenikov
2011-06-28 14:58 ` Dmitry Eremin-Solenikov
2011-06-28 15:06 ` Catalin Marinas
2011-06-28 15:46 ` Dmitry Eremin-Solenikov
2011-06-28 16:11 ` Catalin Marinas
2011-06-28 22:26 ` Dmitry Eremin-Solenikov
2011-06-29 9:10 ` Catalin Marinas
2011-06-29 11:21 ` Dmitry Eremin-Solenikov
2011-06-28 12:07 ` Hui Zhu
2011-06-28 12:09 ` Russell King - ARM Linux
2011-06-28 13:22 ` Catalin Marinas [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=20110628132407.GB7255@1n450.cable.virginmedia.net \
--to=catalin.marinas@arm.com \
--cc=dbaryshkov@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=gdb@sourceware.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=teawater@gmail.com \
--cc=yao@codesourcery.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