From owner-freebsd-current@FreeBSD.ORG  Wed Oct 29 14:38:34 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 BCBF216A4CE; Wed, 29 Oct 2003 14:38:34 -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 AD5C243F93; Wed, 29 Oct 2003 14:38:33 -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 5FA2066B9B; Wed, 29 Oct 2003 14:38:33 -0800 (PST)
Received: by rot13.obsecurity.org (Postfix, from userid 1000)
	id 2C9CB840; Wed, 29 Oct 2003 14:38:33 -0800 (PST)
Date: Wed, 29 Oct 2003 14:38:33 -0800
From: Kris Kennaway <kris@obsecurity.org>
To: Scott Long <scottl@freebsd.org>
Message-ID: <20031029223833.GA13129@rot13.obsecurity.org>
References: <3F92E129.10307@veidit.net>
	<20031028034630.GC32916@VARK.homeunix.com>
	<20031028090337.E27950@carver.gumbysoft.com> <3FA01F71.1020203@adminforum.se>
	<20031029211951.GA12398@rot13.obsecurity.org>
	<20031029152202.C7702@pooker.samsco.home>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="gBBFr7Ir9EOA20Yy"
Content-Disposition: inline
In-Reply-To: <20031029152202.C7702@pooker.samsco.home>
User-Agent: Mutt/1.4.1i
cc: David Schultz <das@freebsd.org>
cc: John Angelmo <john@adminforum.se>
cc: current@freebsd.org
cc: Kris Kennaway <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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Oct 2003 22:38:34 -0000


--gBBFr7Ir9EOA20Yy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Oct 29, 2003 at 03:28:32PM -0700, Scott Long wrote:

> I just tried running the Diablo JDK under -current from yesterday (with
> the libm fix from a few days ago).  It does not look good; possibly an
> issue with both the compat libc and native libc being linked in?  Maybe
> libm.so is still bringing in the native libc.so?  We don't install the
> 4.x libm into compat, and I don't have any 4.x machine around to steal it
> from, so I can't test out that theory.

The binary is linked to:

/usr/lib/libm.so.2
/usr/lib/compat/libc.so.4
(and others)

(recall: the source of the libm problems was that libc.so.5 was *not*
linked in).  I'm not sure why gdb says otherwise - perhaps it's
confused about the library paths.

Perhaps there's some kind of ABI problem here that java is choking on.

Kris
--gBBFr7Ir9EOA20Yy
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/oEFoWry0BWjoQKURAmyEAJ0QuHS/l/cV2WZB9XyRwZHJN83iYwCghMaN
F5lFzz/j9tKAm6HBwEPwqk4=
=zhAt
-----END PGP SIGNATURE-----

--gBBFr7Ir9EOA20Yy--