From owner-freebsd-current@freebsd.org  Fri Jan 27 23:59:09 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0147BCC4721
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 27 Jan 2017 23:59:09 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3])
 by mx1.freebsd.org (Postfix) with ESMTP id E4F4F75E
 for <freebsd-current@freebsd.org>; Fri, 27 Jan 2017 23:59:08 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: by mailman.ysv.freebsd.org (Postfix)
 id E1695CC4720; Fri, 27 Jan 2017 23:59:08 +0000 (UTC)
Delivered-To: current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1164CC471F
 for <current@mailman.ysv.freebsd.org>; Fri, 27 Jan 2017 23:59:08 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id AB30675D
 for <current@FreeBSD.org>; Fri, 27 Jan 2017 23:59:08 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
 by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id v0RNx1FZ022019;
 Fri, 27 Jan 2017 15:59:05 -0800 (PST)
 (envelope-from truckman@FreeBSD.org)
Message-Id: <201701272359.v0RNx1FZ022019@gw.catspoiler.org>
Date: Fri, 27 Jan 2017 15:59:01 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
Subject: Re: malloc() call somehow calling the rtld malloc() implementaion
To: janm@transactionware.com
cc: current@FreeBSD.org
In-Reply-To: <FF5FFDD1-FEDD-4876-872F-94D089C342E8@transactionware.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jan 2017 23:59:09 -0000

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.