This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH 14/17 v5] Avoid stack-protecting signal-handling functions sibcalled from assembly.
- From: Nix <nix at esperi dot org dot uk>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Sun, 15 May 2016 11:39:06 +0100
- Subject: Re: [PATCH 14/17 v5] Avoid stack-protecting signal-handling functions sibcalled from assembly.
- Authentication-results: sourceware.org; auth=none
- References: <1457882222-22599-1-git-send-email-nix at esperi dot org dot uk> <1457882222-22599-15-git-send-email-nix at esperi dot org dot uk> <3a1025f2-8b0e-5d9b-01c4-7b4e4ef62cc8 at redhat dot com> <87r3d3odkd dot fsf at esperi dot org dot uk>
On 15 May 2016, firstname.lastname@example.org told this:
> To be specific, because of this rebuild error, sigjmp.c stays
> stack-protected, so we see this:
As anyone with working eyes should have seen (but I didn't), this was a
*different* problem. (I shouldn't drop the already-merged stuff from my
patch tree and then try building against a tree that doesn't have them
merged in anywhere!)
We do indeed appear to get no problems if dropping the sigjmp stuff,
though I have no idea why not. Clearly the code inspection that led me
to believe I needed to do this was erronous, at least on x86*. Running
tests on other arches now.
NULL && (void)