This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH roland/x86_64-crt1-cfi] BZ#15407: Complete CFI annotations in x86_64 _start code.
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Mon, 29 Apr 2013 09:15:47 -0700
- Subject: Re: [PATCH roland/x86_64-crt1-cfi] BZ#15407: Complete CFI annotations in x86_64 _start code.
- References: <20130426212636 dot 264322C061 at topped-with-meat dot com> <CAMe9rOrSOd0xt9ugCjkXggREx-y35Y3XtMq-b6iuF21MLaovSA at mail dot gmail dot com> <20130427065124 dot 27C1A2C061 at topped-with-meat dot com>
On Fri, Apr 26, 2013 at 11:51 PM, Roland McGrath <roland@hack.frob.com> wrote:
> Why wasn't this CC'd to the list?
I am still getting used to the new gmail interface.
>> I tried the same thing and it didn't work. This is before the
>> first valid frame and unwind shouldn't get here.
>
> What does "valid frame" mean? The _start frame is the outermost
> frame and unwind should get exactly that far. You need to explain
> (in public) exactly what goes wrong in detail, not just make assertions.
All EH frame info should be between crtbeginT.o and crtend.o.
But crt1.o is placed before crtbeginT.o. It is quite odd.
--
H.J.