From owner-freebsd-threads@FreeBSD.ORG Wed Apr 30 17:32:06 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B8A737B401 for ; Wed, 30 Apr 2003 17:32:06 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4D0143FB1 for ; Wed, 30 Apr 2003 17:32:05 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by sccrmhc02.attbi.com (sccrmhc02) with ESMTP id <20030501003204002006jkdte>; Thu, 1 May 2003 00:32:04 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA66600; Wed, 30 Apr 2003 17:32:03 -0700 (PDT) Date: Wed, 30 Apr 2003 17:32:02 -0700 (PDT) From: Julian Elischer To: Terry Lambert In-Reply-To: <3EB0695F.71CA977F@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org cc: Daniel Eischen Subject: Re: Question about rtld-elf. Anyone?.. Anyone? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 00:32:06 -0000 What would be cool would be a signal handler for SIGUSR1 or something that dumps out (to somewhere) a full thread state table. On Wed, 30 Apr 2003, Terry Lambert wrote: > Daniel Eischen wrote: > > As an experiment, I made the dlfoo calls in rtld-elf weak > > (__dlfoo -> dlfoo) and then overrode them in libpthread > > and protected them with mutexes. > > > > I can get mozilla to work about 1/2 of the time now, but > > it still gets stuck in the same state the other 1/2 of > > the time. This is a bit of an improvement, and seems to > > indicate (at least to me) that rtld-elf is the culprit. > > > Is there maybe a way to get the thread that was running when > the process was involuntarily preempted run first, instead of > running it based on priority? Netscape, at least, made this > assumption for Java and Javascript pages. > > Alternately, you may try disabling Java* in Mozilla, and see > if that keeps you from crashing. > > Also try not moving the mouse until everything is loaded, and > see if that saves you, too. > > -- Terry > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" >