From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 6 21:50:07 2007 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AAFE316A468 for ; Wed, 6 Jun 2007 21:50:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 982F713C4C2 for ; Wed, 6 Jun 2007 21:50:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l56Lo7Ka022870 for ; Wed, 6 Jun 2007 21:50:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l56Lo7rG022869; Wed, 6 Jun 2007 21:50:07 GMT (envelope-from gnats) Date: Wed, 6 Jun 2007 21:50:07 GMT Message-Id: <200706062150.l56Lo7rG022869@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Kris Kennaway Cc: Subject: Re: amd64/110655: [threads] 32 bit threaded applications crash on amd64 SMP kernel. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kris Kennaway List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2007 21:50:07 -0000 The following reply was made to PR amd64/110655; it has been noted by GNATS. From: Kris Kennaway To: Jeff Wheelhouse Cc: Kris Kennaway , bug-followup@FreeBSD.org Subject: Re: amd64/110655: [threads] 32 bit threaded applications crash on amd64 SMP kernel. Date: Wed, 6 Jun 2007 17:42:38 -0400 On Wed, Jun 06, 2007 at 05:11:25PM -0400, Jeff Wheelhouse wrote: > Kris Kennaway wrote: > >-m32 doesn't DTRT on FreeBSD, can you confirm that this problem exists > >with a binary compiled by an i386 compiler? > > I can. > > $ uname -m > i386 > $ cc -o crash32-thr crash32.c -lthr > $ cc -o crash32-pthread crash32.c -pthread > $ md5 crash32-thr crash32-pthread > MD5 (crash32-thr) = 91aea395dd2c5798d7cba9a216c4c227 > MD5 (crash32-pthread) = a590f1c97e5ec11ddc94fa3d7f4bf167 > $ ./crash32-thr > Thread. > $ ./crash32-pthread > Thread. > $ > > $ uname -m > amd64 > $ md5 crash32-thr crash32-pthread > MD5 (crash32-thr) = 91aea395dd2c5798d7cba9a216c4c227 > MD5 (crash32-pthread) = a590f1c97e5ec11ddc94fa3d7f4bf167 > $ ./crash32-thr > Bad system call(coredump) > $ ./crash32-pthread > Memory fault(coredump) > $ OK, that's useful to know. I ran into a problem myself that looked similar but wanted to check first (I didn't isolate it to libthr yet). Kris