Date: Fri, 8 Jun 2001 08:49:44 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: Idea Receiver <receiver@blueskybbs.yi.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: pthread and write() Message-ID: <Pine.SUN.3.91.1010608084824.17428A-100000@pcnet1.pcnet.com> In-Reply-To: <Pine.BSF.4.21.0106082227510.458-100000@RedDust.BlueSky.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 8 Jun 2001, Idea Receiver wrote: > I dont know if this is cause by -current, I have not yet try on the > -stable. However, I just write here, maybe someone can help me.. :P > > recently, I wrote a multithread network server for my work. what it does > is to accept TCP connection from remote, and then put it into a new > thread. I have wrote a simulation client to test this application i > wrote. The simulation client will keep opening multi connection to the > server, and keep sent a 8byte structure to server using loop and > sleep(1) in between each write(). Also each of the thread created by > server will simply reply a 8byte structure to its client (using > write() again). > > When the client bring up "enough" (between 300-1000) connection to > the server, then the server will core dump around 30mis to 1hr time. > After I trace the problem, I found it is cause by write() with signal > 11. then i use gdb to trace out the problem. follow is what i get from > gdb: > > Program received signal SIGSEGV, Segmentation fault. > 0x28121637 in _fd_lock_backout () from /usr/lib/libc_r.so.4 You're not running -current if you're using libc_r.so.4. We're at libc_r.so.5. And fd locks have also been disabled in -current. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.1010608084824.17428A-100000>