Date: Fri, 29 Sep 2000 21:41:45 +0200 (CEST) From: Ron Scott <ron@GeP18-5.NyirCaTv.BroadBand.hu> To: freebsd-stable@FreeBSD.ORG Subject: Re: pthreads bug? Message-ID: <Pine.BSF.4.21.0009292136570.20078-100000@gep18-5.nyircatv.broadband.hu> In-Reply-To: <20000929013521.C27736@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Today Alfred Perlstein wrote: > * Roman Shterenzon <roman@harmonic.co.il> [000929 01:23] wrote: > > Hello, > > I noticed some strange behavior in pthreads applications, > > close on socket which is in accept() will be blocked untill there's a connection > > to port and accept returns. > > It's observed on 4.0 - 4.1-STABLE, perhaps 4.1.1-STABLE as well, but I didn't > > try it. I don't have 3.5.1-STABLE system to test it there. > > It affects, for example, openldap - start it , then kill -15 it. > > It won't die (and it should). Now, try to telnet localhost 389 ; now it died. > > The same behavior is a program we're writing right now, it's very annoying, in > > fact we don't know how to deal with it. It works on solaris and linux. > > btw, linux doesn't dump core on threaded application, how one's supposed to > > debug it? > > No clue on that one. :( > Maybe with abort(), raise(SIGSEGV), kill(getpid(), SIGSEGV) ??? Cheers, -Ron -- UNIX was never designed to keep people from doing stupid things, because that policy would also keep them from doing clever things. (Doug Gwyn) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0009292136570.20078-100000>