From owner-freebsd-current Fri Jun 8 5:51:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from RedDust.bluesky.net.au (CPE-61-9-142-80.vic.bigpond.net.au [61.9.142.80]) by hub.freebsd.org (Postfix) with ESMTP id 7F3C837B40D for ; Fri, 8 Jun 2001 05:51:06 -0700 (PDT) (envelope-from receiver@blueskybbs.yi.org) Received: from localhost (receiver@localhost) by RedDust.bluesky.net.au (8.11.1/8.11.0) with ESMTP id f57BXNu44724 for ; Thu, 7 Jun 2001 21:33:24 +1000 (EST) (envelope-from receiver@blueskybbs.yi.org) Date: Thu, 7 Jun 2001 21:33:22 +1000 (EST) From: Idea Receiver To: current@freebsd.org Subject: pthread and write() Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 can anyone plz help with this problem? is there anything important I missed? thx!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message