Re: [patch] i386: fix one case of stuck dwarf2 unwinder II

>> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch] i386: fix one case of stuck dwarf2 unwinder II
    • From: Andi Kleen <[email protected]>

• References:
  • Re: [patch] i386: fix one case of stuck dwarf2 unwinder II
    • From: Chuck Ebbert <[email protected]>

• Prev by Date: Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion
• Next by Date: Re: [patch] i386: fix one case of stuck dwarf2 unwinder II
• Previous by thread: Re: [patch] i386: fix one case of stuck dwarf2 unwinder II
• Next by thread: Re: [patch] i386: fix one case of stuck dwarf2 unwinder II
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]