Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Jan 2017 15:59:01 -0800 (PST)
From:      Don Lewis <truckman@FreeBSD.org>
To:        janm@transactionware.com
Cc:        current@FreeBSD.org
Subject:   Re: malloc() call somehow calling the rtld malloc() implementaion
Message-ID:  <201701272359.v0RNx1FZ022019@gw.catspoiler.org>
In-Reply-To: <FF5FFDD1-FEDD-4876-872F-94D089C342E8@transactionware.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 28 Jan, Jan Mikkelsen wrote:
> Hi,
> 
> Are you being affected by this rtld behaviour:
> 
> https://lists.freebsd.org/pipermail/freebsd-hackers/2016-July/049769.html <https://lists.freebsd.org/pipermail/freebsd-hackers/2016-July/049769.html>;
> 
> https://lists.freebsd.org/pipermail/freebsd-stable/2015-July/082751.html <https://lists.freebsd.org/pipermail/freebsd-stable/2015-July/082751.html>;
> 
> (I still find this a bit scary.)

That's not rtld, it's the kernel linker.  Yes, I have also encountered
that, though in my case the effect was that it hid the fact that the
target symbol was not exported.  There was a linking failure on i386,
which the amd64-only testing did not uncover.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201701272359.v0RNx1FZ022019>