From owner-freebsd-amd64@FreeBSD.ORG  Sat Jun  5 10:11:57 2004
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4459E16A4CE; Sat,  5 Jun 2004 10:11:57 -0700 (PDT)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 02AC943D48; Sat,  5 Jun 2004 10:11:57 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i55HButD028509;
	Sat, 5 Jun 2004 13:11:56 -0400 (EDT)
Date: Sat, 5 Jun 2004 13:11:56 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Sean McNeil <sean@mcneil.com>
In-Reply-To: <1086453979.18813.0.camel@server.mcneil.com>
Message-ID: <Pine.GSO.4.10.10406051310350.14185-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Tim Robbins <tim@robbins.dropbear.id.au>
cc: freebsd-amd64@freebsd.org
cc: freebsd-threads@freebsd.org
Subject: Re: All my amd64 problems appear to be KSE
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jun 2004 17:11:57 -0000

On Sat, 5 Jun 2004, Sean McNeil wrote:

> On Sat, 2004-06-05 at 09:40, Sean McNeil wrote:
> > On Sat, 2004-06-05 at 09:31, Tim Robbins wrote:
> > 
> > > Everything seems to work fine if I build libpthread with SYSTEM_SCOPE_ONLY
> > > (at least it hasn't crashed so far.) My current guess is that there's a
> > > bug in context manipulation or signals. I initially thought we weren't
> > > saving enough FPU context in _amd64_save_context, but adding an fxsave
> > > in there didn't help.
> > 
> > I see a problem with bash and signals too when libpthread is involved. 
> > It would core dump when I resize a window.  I use nss_ldap and it was
> > pulling in pthread through db41.  I solved my issue by rebuilding db41
> > to eliminate pthread from the libdb41.so.1.  Perhaps tracing this down
> > would be useful?
> 
> resize of bash causes error like this:
> 
> #0  _thr_sig_handler (sig=28, info=0x100, ucp=0x201701904)
>     at /usr/src/lib/libpthread/thread/thr_sig.c:373
> #1  0x00000002006ae9b0 in _rl_savestring () from /lib/libreadline.so.4
> #2  <signal handler called>
> #3  0x0000000200a822ec in read () from /lib/libc.so.5
> #4  0x00000002006ab113 in rl_getc () from /lib/libreadline.so.4
> #5  0x00000002006ab0c9 in rl_read_key () from /lib/libreadline.so.4
> #6  0x00000002006bdeb7 in readline_internal_char () from
> /lib/libreadline.so.4

That all looks fine, but bash isn't threaded is it?

-- 
Dan Eischen