mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Reiner Herrmann <reiner@reiner-h.de>
To: musl@lists.openwall.com
Subject: Segmentation fault in static binaries built with recent binutils
Date: Wed, 18 Jul 2018 18:39:40 +0200	[thread overview]
Message-ID: <20180718163940.gnx6jkia4i5qdjua@reiner-h.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 839 bytes --]

Hi,

Debian recently updated binutils from 2.30 to 2.31.
When compiling simple static binaries with musl (1.19 and git)
they segfault on startup (dynamic linking still works fine).
With the previous binutils version it is running successfully.

  $ cat test.c 
  int main() { return 0; }
  $ musl-gcc -ggdb3 -O0 -static test.c
  $ gdb ./a.out 
  GNU gdb (Debian 8.1-3) 8.1
  [...]
  Reading symbols from ./a.out...done.
  (gdb) run
  Starting program: /tmp/test/a.out 
  
  Program received signal SIGSEGV, Segmentation fault.
  0x000000000040159d in static_init_tls ()
  (gdb) bt
  #0  0x000000000040159d in static_init_tls ()
  #1  0x0000000000000000 in ?? ()

See also: https://ci.debian.net/packages/m/musl/unstable/amd64/

Is this a bug in musl or should I report it to binutils?

Kind regards,
   Reiner

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2018-07-18 16:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 16:39 Reiner Herrmann [this message]
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
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=20180718163940.gnx6jkia4i5qdjua@reiner-h.de \
    --to=reiner@reiner-h.de \
    --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).