From owner-freebsd-current@FreeBSD.ORG Thu Oct 30 23:04:23 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C47E16A4CE; Thu, 30 Oct 2003 23:04:23 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 023AA43F75; Thu, 30 Oct 2003 23:04:22 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id D42A366D6A; Thu, 30 Oct 2003 23:04:16 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id AA18786B; Thu, 30 Oct 2003 23:04:16 -0800 (PST) Date: Thu, 30 Oct 2003 23:04:16 -0800 From: Kris Kennaway To: "M. Warner Losh" Message-ID: <20031031070416.GA35316@rot13.obsecurity.org> References: <20031029211951.GA12398@rot13.obsecurity.org> <20031029152202.C7702@pooker.samsco.home> <20031029154141.T7702@pooker.samsco.home> <20031030.234813.72025638.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline In-Reply-To: <20031030.234813.72025638.imp@bsdimp.com> User-Agent: Mutt/1.4.1i cc: das@freebsd.org cc: john@adminforum.se cc: current@freebsd.org cc: kris@obsecurity.org Subject: Re: __fpclassifyd problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2003 07:04:23 -0000 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 30, 2003 at 11:48:13PM -0700, M. Warner Losh wrote: > In message: <20031029154141.T7702@pooker.samsco.home> > Scott Long writes: > : To respond to myself, I got ahold of a 4.8 libm.so and made sure that t= he > : linker used it. No change in the problem, and it still hints that the > : native libc is being linked in. >=20 > You might want to enable debugging of ld.so to confirm. This was understood already (java is doing a dlopen of /usr/lib/libc.so). Kris --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/oglwWry0BWjoQKURAiXTAJ9pJmv0plPRe0hP/0AYViuMkkIs2QCg3AzR QcMCLGBSJFc0WA1U1qXzJr4= =I4eO -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE--