Date: Fri, 27 Jun 2003 08:59:36 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: threads@freebsd.org Subject: Re: libkse / libthr bugs? Message-ID: <200306271559.h5RFxaQT043908@strings.polstra.com> In-Reply-To: <20030627012456.YLSF27254.pop017.verizon.net@kokeb.ambesa.net> References: <3EFB2E12.3080504@intalio.com> <20030627002155.UEBC11703.pop018.verizon.net@kokeb.ambesa.net> <20030627003922.GA38103@dhcp01.pn.xcllnt.net> <20030627012456.YLSF27254.pop017.verizon.net@kokeb.ambesa.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20030627012456.YLSF27254.pop017.verizon.net@kokeb.ambesa.net>, Mike Makonnen <mtm@identd.net> wrote: > On Thu, 26 Jun 2003 17:39:22 -0700 > Marcel Moolenaar <marcel@xcllnt.net> wrote: > > On Thu, Jun 26, 2003 at 08:21:54PM -0400, Mike Makonnen wrote: > > > > Thread (_thread_initial:0) already on mutexq > > > > Fatal error 'Illegal call from signal handler' at line 1347 in file > > > > /nfs/freebsd/5.x/src/lib/libthr/thread/thr_mutex.c (errno = 0) > > > > > > Great! I've been waiting for this message to appear for some time. Do you > > > have a backtrace by any chance? > > > > gdb(1) hasn't been ported yet, so no. > > BTW: The thread is not always _thread_initial... > > hmm.. ok if it's not always thread initial, that's gonna make it a bit harder. I saw it happen to libthr's "GC" thread yesterday: Thread (GC:3) already on mutexq Fatal error 'Illegal call from signal handler' at line 1347 in file /a/src/lib/libthr/thread/thr_mutex.c (errno = 35) John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Two buttocks cannot avoid friction." -- Malawi saying
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200306271559.h5RFxaQT043908>