From owner-freebsd-current@FreeBSD.ORG Mon Jun 9 19:13:59 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F03037B401 for ; Mon, 9 Jun 2003 19:13:59 -0700 (PDT) Received: from mx1.mail.ru (mx1.mail.ru [194.67.23.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D69743FB1 for ; Mon, 9 Jun 2003 19:13:58 -0700 (PDT) (envelope-from kabaev@mail.ru) Received: from [141.154.215.134] (port=53798 helo=kan.dnsalias.net) by mx1.mail.ru with esmtp id 19PYe4-000DQx-00; Tue, 10 Jun 2003 06:13:57 +0400 Received: from kan.dnsalias.net (ak03@localhost [127.0.0.1]) by kan.dnsalias.net (8.12.9/8.12.9) with ESMTP id h5A2DaHE020482; Mon, 9 Jun 2003 22:13:36 -0400 (EDT) (envelope-from kan@kan.dnsalias.net) Received: (from kan@localhost) by kan.dnsalias.net (8.12.9/8.12.9/Submit) id h5A2DZGM020481; Mon, 9 Jun 2003 22:13:36 -0400 (EDT) Date: Mon, 9 Jun 2003 22:13:35 -0400 From: Alexander Kabaev To: Bruno Afonso Message-Id: <20030609221335.31db11bf.kabaev@mail.ru> In-Reply-To: <3EE53963.6000509@dequim.ist.utl.pt> References: <3EE53963.6000509@dequim.ist.utl.pt> X-Mailer: Sylpheed version 0.9.0claws2 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam: Not detected cc: current@freebsd.org Subject: Re: libthr.so lib - crashes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2003 02:13:59 -0000 On Tue, 10 Jun 2003 02:50:27 +0100 Bruno Afonso wrote: > Hello, > > I'm using -current from monday and I'm having a lot of crashes on my > athlon 2.4+. So far, I've had to stop using it with mozilla 1.4b, > FireBird and now it seems to crash pymol too. (python based) > I think it's libth library as I don't get crashes without libthr :) > > How can I help you guys with this? Am I the only one having problems > with these apps (ok, pymol is not widely used)? > > The crash simply "locks" the apps, and one can only kill it. There's > not way to "normally" close it. Just from the top of my head: Drop into ddb and run look what 'ps' command reports for the stuck process. Do a 'trace ' in DDB and see what a kernel backtrace looks like. Use gencore to grab a core of the process to see it's userland backtrace. Send all of the above to relevant people and/or threads@ mailing list.