From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Re: Segmentation fault in static binaries built with recent binutils
Date: Wed, 18 Jul 2018 23:37:22 +0200 [thread overview]
Message-ID: <20180718213721.GP4418@port70.net> (raw)
In-Reply-To: <20180718205320.tsud6pgbxjkdrwrw@reiner-h.de>
* Reiner Herrmann <reiner@reiner-h.de> [2018-07-18 22:53:20 +0200]:
> On Wed, Jul 18, 2018 at 10:19:28PM +0200, Szabolcs Nagy wrote:
> > the difference between the two cases was --build-id
> >
> > --build-id=sha1 works, --build-id=none segfaults
> >
> > i assume the note section with the build id happens
> > to force ld to keep the initial load segment, but
> > that should be there without any note section, so
> > it's likely a binutils bug (i see it on 2.30 and
> > master branch too)
>
> Do you mean you see the bug on 2.30, or the initial load segment?
> Because with 2.30 it's working for me (the initial load segment is there).
>
> Thanks for your investigation and the suggested workaround!
>
i opened
https://sourceware.org/bugzilla/show_bug.cgi?id=23428
i see the same behaviour on debian sid with
$ ld --version
GNU ld (GNU Binutils for Debian) 2.30.90.20180710
Copyright (C) 2018 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty.
i haven't bisected the issue but i suspect both
2.30 and 2.31 branches are affected by some recent
change (but not the initial 2.30 release).
next prev parent reply other threads:[~2018-07-18 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 16:39 Reiner Herrmann
2018-07-18 17:37 ` Rich Felker
2018-07-18 18:14 ` Reiner Herrmann
2018-07-18 19:00 ` Szabolcs Nagy
2018-07-18 19:38 ` Szabolcs Nagy
2018-07-18 20:19 ` Szabolcs Nagy
2018-07-18 20:24 ` Szabolcs Nagy
2018-07-18 20:50 ` Rich Felker
2018-07-18 20:53 ` Reiner Herrmann
2018-07-18 21:37 ` Szabolcs Nagy [this message]
2018-07-18 21:49 ` Reiner Herrmann
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=20180718213721.GP4418@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).