mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: "Chuck Ebbert" <76306.1226@compuserve.com>, "Andi Kleen" <ak@suse.de>
Cc: "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, 07 Aug 2006 09:00:34 +0100	[thread overview]
Message-ID: <44D70F42.76E4.0078.0@novell.com> (raw)
In-Reply-To: <200608061212_MC3-1-C747-C2AD@compuserve.com>

>> 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).

Jan

  reply	other threads:[~2006-08-07  8:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-06 16:09 Chuck Ebbert
2006-08-07  8:00 ` Jan Beulich [this message]
2006-08-07  8:04   ` Andi Kleen
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=44D70F42.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=76306.1226@compuserve.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.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
Powered by JetHome