From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: "Chuck Ebbert" <76306.1226@compuserve.com>,
"Jesper Juhl" <jesper.juhl@gmail.com>,
"Andrew Morton" <akpm@osdl.org>, "Dave Jones" <davej@redhat.com>,
"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [patch] i386: fix one case of stuck dwarf2 unwinder II
Date: Mon, 7 Aug 2006 10:04:37 +0200 [thread overview]
Message-ID: <200608071004.37849.ak@suse.de> (raw)
In-Reply-To: <44D70F42.76E4.0078.0@novell.com>
On Monday 07 August 2006 10:00, Jan Beulich wrote:
> >> Yes that's the problem. If you check for <= stext/_stext then the unwinder
> >> won't catch the L6 (which is above it) and report a "stuck" again
> >
> >Maybe I'm being dense here, but:
> >
> >c0100210 t L6
> >c0100212 t check_x87
> >c010023a t setup_idt
> >c0100257 t rp_sidt
> >c0100264 t ignore_int
> >c0100298 T stext
> >c0100298 T _stext
> >
> >It looks like L6 is before _stext to me.
>
> So it would seem to me. Nevertheless, in my opinion the proper fix is to annotate the call site
> (in head.S) to specify a zero EIP as return address (which denotes the bottom of a frame).
Can you please send a patch to do that?
That seems to be missing in some other places too, e.g. i386 sysenter path, x86-64 kernel_thread,
more?
-Andi
next prev parent reply other threads:[~2006-08-07 8:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 16:09 [patch] i386: fix one case of stuck dwarf2 unwinder II Chuck Ebbert
2006-08-07 8:00 ` Jan Beulich
2006-08-07 8:04 ` Andi Kleen [this message]
2006-08-15 10:33 ` Jan Beulich
2006-08-15 10:47 ` Andi Kleen
2006-08-15 10:54 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2006-08-06 7:11 Chuck Ebbert
2006-08-06 14:04 ` Andi Kleen
2006-08-06 5:00 [patch] i386: fix one case of stuck dwarf2 unwinder Chuck Ebbert
2006-08-06 6:05 ` [patch] i386: fix one case of stuck dwarf2 unwinder II Andi Kleen
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=200608071004.37849.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=jbeulich@novell.com \
--cc=jesper.juhl@gmail.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