From: Hugues Bruant <hugues@aerofs.com>
To: musl@lists.openwall.com
Subject: Re: dynlink.c: bug in reclaim_gaps leading to segfault in __libc_exit_fini
Date: Wed, 17 Feb 2016 01:16:55 -0500 [thread overview]
Message-ID: <CA+bHwpp_UXDEVY2jY9ALwPSKoJ7zeXdNEHQ1cTo_EojU9svMZg@mail.gmail.com> (raw)
In-Reply-To: <20160217002123.GB9349@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
I packaged a small reproducer in a docker image:
docker run huguesb/dmg-musl-crash-repro dmg build /repro.dmg.hfs /repro.dmg
Should successfully create a dmg from the hfs file and return exit code 139
due to the segfault in __libc_exit_fini
The failure is 100% reproducible on all the hosts I've tried so far, which
gives me some confidence that it's not a bad interaction with the kernel:
- boot2docker 1.10.1 with kernel 4.1.17 / docker 1.10.1 / aufs
- CoreOS 899.6.0 with kernel 4.3.3 / docker 1.9.1 / overlayfs
- Ubuntu 14.04 with kernel 3.19.0-43 / docker 1.9.1 / aufs
- Alpine 3.3.1 with kernel 4.1.15 / docker 1.9.1 / overlayfs
Although my main use case is for this to run inside a container, for
completeness I copied the hfs file out of the docker image on the alpine
host (docker cp). The issue still manifests, which rules out any bad
interaction with docker.
Please let me know if there's anything more I can do.
Regards,
Hugues
[-- Attachment #2: Type: text/html, Size: 1181 bytes --]
next prev parent reply other threads:[~2016-02-17 6:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 21:30 Hugues Bruant
2016-02-16 21:55 ` Szabolcs Nagy
2016-02-16 22:02 ` Rich Felker
2016-02-17 0:05 ` Hugues Bruant
2016-02-17 0:21 ` Rich Felker
2016-02-17 6:16 ` Hugues Bruant [this message]
2016-02-17 6:27 ` Hugues Bruant
2016-02-17 7:03 ` Timo Teras
2016-02-17 9:15 ` Hugues Bruant
2016-02-17 15:25 ` Rich Felker
2016-02-17 17:34 ` Hugues Bruant
2016-02-17 18:14 ` Szabolcs Nagy
2016-02-17 18:46 ` Isaac Dunham
2016-02-17 10:19 ` Szabolcs Nagy
2016-02-18 18:05 ` Szabolcs Nagy
2016-02-18 18:33 ` Rich Felker
2016-02-17 15:17 ` Markus Wichmann
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=CA+bHwpp_UXDEVY2jY9ALwPSKoJ7zeXdNEHQ1cTo_EojU9svMZg@mail.gmail.com \
--to=hugues@aerofs.com \
--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).