From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: musl segfaulting when compiled with -O2
Date: Tue, 7 Mar 2017 15:39:05 -0500 [thread overview]
Message-ID: <20170307203905.GT1520@brightrain.aerifal.cx> (raw)
In-Reply-To: <20170307203234.GC18936@gmail.com>
On Tue, Mar 07, 2017 at 05:32:35PM -0300, Breno Leitao wrote:
> Musl package on Debian on ppc64le is broken.
>
> When running any software with it, it segfaults. Doing a little bit of
> debugging I found that libc.so is broken.
>
> I got the upstream code, and found that the problme is also
> reproducible.
>
> I found that the problem only happen when compiling with -O2 and -O3. If
> I compile musl with -O1 or -O0, the problm does not happen.
>
> This is the bt of the code that crashes:
>
> (gdb) bt
> #0 0x0000000148b84dc0 in ?? ()
> #1 0x0000000048bdb8dc in _dlstart_c (sp=0x3fffc33294b0, dynv=<optimized out>) at ldso/dlstart.c:147
> #2 0x0000000048bdebe0 in _dlstart ()
>
> (gdb) up
> #1 0x0000000048bdb8dc in _dlstart_c (sp=0x3fffc33294b0, dynv=<optimized out>) at ldso/dlstart.c:147
> 147 dls2((void *)base, sp);
>
> $ gcc --version
> gcc (Debian 6.3.0-5) 6.3.0 20170124
>
> Not sure if this is a GCC issue or a musl issue now.
Can you post the crashing libc.so somewhere? Depending on how they're
building it, the problem could be in various different places. A
glibc-targeted powerpc* gcc is not suitable for compiling musl, since
it has various ABI mismatches, but that's probably not what you're
seeing here even if one was used.
Rich
next prev parent reply other threads:[~2017-03-07 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 20:32 Breno Leitao
2017-03-07 20:39 ` Rich Felker [this message]
2017-03-07 20:55 ` Breno Leitao
2017-03-07 21:45 ` Rich Felker
2017-03-08 1:18 ` Szabolcs Nagy
2017-03-08 2:28 ` Rich Felker
2017-03-08 14:19 ` Breno Leitao
2017-03-08 18:39 ` Rich Felker
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=20170307203905.GT1520@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).