Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190531133424.GO23599@brightrain.aerifal.cx>
Date: Fri, 31 May 2019 09:34:24 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Hijacking malloc called within musl libc

On Fri, May 31, 2019 at 01:43:17PM +0200, Szabolcs Nagy wrote:
> * sva sva <azharivs@...il.com> [2019-05-31 00:13:27 -0400]:
> > I am interposing all malloc/calloc/realloc/free/memalign but still the
> > realloc in scandir gets called from musl's libc. Does that make sense?
> 
> no.
> 
> it works for me as expected.
> 
> you need to write down what you did, what you expected and what you got instead.
> (how did you verify that the musl internal realloc gets called?
> it can be a bug in your interposer, in your static linker, in ...)

It's almost certainly a matter of using a pre-1.1.20 version of musl,
or having an old config.mak from pre-1.1.20 musl (with
-Bsymbolic-functions) rather than re-running configure with the
current version.

Rich

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.