From owner-freebsd-threads@FreeBSD.ORG Wed Apr 30 17:39: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 97B0737B401 for ; Wed, 30 Apr 2003 17:39:53 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id D98E943FBF for ; Wed, 30 Apr 2003 17:39:52 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from pcnet1.pcnet.com (localhost [127.0.0.1]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h410dmBg006019; Wed, 30 Apr 2003 20:39:48 -0400 (EDT) Received: from localhost (eischen@localhost)h410dlHl006015; Wed, 30 Apr 2003 20:39:47 -0400 (EDT) Date: Wed, 30 Apr 2003 20:39:47 -0400 (EDT) From: Daniel Eischen To: Julian Elischer In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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:39:53 -0000 On Wed, 30 Apr 2003, Julian Elischer wrote: > What would be cool would be a signal handler for SIGUSR1 > or something that dumps out (to somewhere) a full thread state table. Where have you been? We've had that in libc_r, libthr (I believe), and libpthread via SIGINFO :-) The problem is that rtld-elf uses sigprocmask to block all the signals within its critical regions, so only SIGKILL works. I've made some local changes to rtld-elf just to test out different theories, but it's beyond me (well, I don't really want to devote lots of time trying to understand all the inner workings of it) to make the kind of changes that jdp had mentioned. > 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 -- Dan Eischen