mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rob Landley <rob@landley.net>
To: musl@lists.openwall.com
Subject: Re: libc.so segfaults on mips
Date: Thu, 4 Sep 2014 12:17:57 -0500	[thread overview]
Message-ID: <CAOS_Y6Q5yo8FwiwSHoQugw+kLvxd-OPvb+qRP9TM-547eRmrFQ@mail.gmail.com> (raw)
In-Reply-To: <20140904155857.GT12888@brightrain.aerifal.cx>

On Thu, Sep 4, 2014 at 10:58 AM, Rich Felker <dalias@libc.org> wrote:
> On Thu, Sep 04, 2014 at 11:20:32PM +0800, Рысь wrote:
>>
>>
>> 4 сентября 2014 г. 22:57:01 KRAT, Rich Felker <dalias@libc.org> пишет:
>>
>> >This output looks incomplete. MIPS readelf -a output should end with a
>> >large section that starts with:
>> >
>> >Primary GOT:
>> > Canonical gp value: 000b2f90
>> >
>> >followed by
>> >
>> > Local entries:
>> >  ...
>> >
>> > Global entries:
>> >  ...
>> >
>> >This is where I would be able to tell if something is wrong. Do you
>> >perhaps have an ancient version of readelf? If you're using the native
>> >one that came with your mips toolchain, try the host readelf instead
>> >from a normal system.
>> >
>> >Rich
>>
>> Yes, it is. The host one is same and generates same output. Had to
>> download file to another machine with binutils 2.21, it is attached.
>> (Or if you want to play with it, here is a compiled libc.so:
>> http://lynxlynx.tk/lynx/libc.so)
>
> I can tell you from reading that readelf output that
> -Bsymbolic-functions was ignored by the linker (or it was patched out
> of your musl build entirely?). For a correctly linked libc.so, the
> local entries list should be huge and the global entries list should
> be very small, referring only to global data symbols, not functions.

I have the same problem in my aboriginal linux toolchain, which is
also the last gplv2 releases of gcc and binutils. (It's not exaclty
being ignored, but it's not working right either.)

Fixing it is on my todo list, but at the moment I'm trying to get a
release out with the new wrapper and uClibc (and linux 3.15) to just
fix part of the problem and have the release version less behind.
(Fixing this shouldn't be all that _hard_, it's just out of scope for
this release which is _already_ hugely overdue...)

Rob


  reply	other threads:[~2014-09-04 17:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04  7:07 Рысь
     [not found] ` <20140904073545.GP12888@brightrain.aerifal.cx>
     [not found]   ` <7bb51525-1a3d-43e8-a567-7523ca3673c7@email.android.com>
2014-09-04 12:32     ` Szabolcs Nagy
2014-09-04 14:03       ` Рысь
2014-09-04 14:45         ` Szabolcs Nagy
2014-09-04 14:56           ` Рысь
2014-09-04 14:57     ` Rich Felker
2014-09-04 15:20       ` Рысь
2014-09-04 15:58         ` Rich Felker
2014-09-04 17:17           ` Rob Landley [this message]
2014-09-04 17:38             ` Laurent Bercot
2014-09-04 17:41               ` Rich Felker
2014-09-04 19:26                 ` Isaac Dunham
2014-09-04 19:48                 ` Rob Landley
2014-09-04 17:48             ` Рысь

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=CAOS_Y6Q5yo8FwiwSHoQugw+kLvxd-OPvb+qRP9TM-547eRmrFQ@mail.gmail.com \
    --to=rob@landley.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).