From owner-freebsd-threads@FreeBSD.ORG Wed Apr 30 17:28:53 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 DC31E37B401 for ; Wed, 30 Apr 2003 17:28:53 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E50B43FB1 for ; Wed, 30 Apr 2003 17:28:53 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0055.cvx22-bradley.dialup.earthlink.net ([209.179.198.55] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19B1wQ-0006RB-00; Wed, 30 Apr 2003 17:28:51 -0700 Message-ID: <3EB0695F.71CA977F@mindspring.com> Date: Wed, 30 Apr 2003 17:25:03 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Daniel Eischen References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a46442b4a032ab4b4e3f0396e2f697675a667c3043c0873f7e350badd9bab72f9c350badd9bab72f9c cc: threads@freebsd.org 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:28:54 -0000 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