Date: Fri, 27 Jun 2003 02:41:28 -0400 From: Mike Makonnen <mtm@identd.net> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: freebsd-threads@FreeBSD.org Subject: Re: libkse / libthr bugs? Message-ID: <20030627064129.DZPG3199.pop016.verizon.net@kokeb.ambesa.net> In-Reply-To: <20030627021706.GA38490@dhcp01.pn.xcllnt.net> References: <3EFB2E12.3080504@intalio.com> <20030626203624.GA37317@dhcp01.pn.xcllnt.net> <20030627002155.UEBC11703.pop018.verizon.net@kokeb.ambesa.net> <20030627003922.GA38103@dhcp01.pn.xcllnt.net> <20030627012456.YLSF27254.pop017.verizon.net@kokeb.ambesa.net> <20030627021706.GA38490@dhcp01.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 26 Jun 2003 19:17:06 -0700 Marcel Moolenaar <marcel@xcllnt.net> wrote: > No improvement: > > : > bar 98 > bar 99 > Thread (GC:2) 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) Abort (core > dumped) > > Is this something you really need a stacktrace of? No. I was only interested in seeing if this caused the "Illigal call...." to go away. > > > If it's expected to make a difference, I can grab them and try again. > > > Just say the word... > > > > If you have the time/inclination. I'll grab them as well and see what > > happens. > > I'll try that this weekend then. I have corresponded briefly with jdp, and from what he tells me there's something really wrong with signal handling in the kernel. I'm inclined to believe him because I've seen some really strange lockups that I can't seem to pin on libthr (even though it still needs some work). I welcome any attempt; however unrelated to libthr, to clean up signal handling there. Cheers. -- Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc mtm@identd.net | D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9 mtm@FreeBSD.Org| FreeBSD - The Power To Serve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030627064129.DZPG3199.pop016.verizon.net>