From owner-freebsd-hackers Wed Mar 19 11:15:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA15698 for hackers-outgoing; Wed, 19 Mar 1997 11:15:03 -0800 (PST) Received: from sendero.i-connect.net ([206.190.144.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA15680 for ; Wed, 19 Mar 1997 11:14:57 -0800 (PST) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.4) id MAA18294 for freebsd-hackers@freebsd.org; Wed, 19 Mar 1997 12:15:22 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD X-PRIORITY: 2 (High) Priority: urgent Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Resent-Date: Tue, 18 Mar 1997 16:07:57 -0800 (PST) Resent-Message-Id: Resent-From: Steve Tarkalson Resent-To: Simon Shapiro Date: Wed, 19 Mar 1997 12:04:14 -0800 (PST) Organization: iConnect Corp. From: Simon Shapiro To: freebsd-hackers@freebsd.org Subject: FW: threads... Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, As many of you knw, we are working on a large/complex project using FreeBSD. Critical part of this effort is porting a complex, high-speed database server from Slowlaris and Linux. It is a multi-threaded application. Following are comments by Steve, our lead developer of the server. He is highly qualified but FreeBSD is new to him. The server works flawlessly on Solaris, using posix Threads and works properly on Linux (againm using Posix threads). Any help will be appreciated. We will even pay for consulting work if necessary. Simon ----- Forwarded Message ----: ----- From: Steve Tarkalson To: Simon Shapiro Subject: threads... Simon, here is a summary of the current problems I am having with threads on FreeBSD: - there is name space collisions between libc and libc_r. supposedly libc_r is a full blown replacement for libc (?). if you link with libc_r, libc gets linked as well. since ld assumes startup files (crt0.o and std lib c). order is important to solve some name space problems but this causes other non-fatal problems - like an empty stub for _thread_init() - threads initialization doesn't occurr (_thread_init). there doesn't seem to be an entry on the Construct list for this guy in libc_r. even though I have explicitly called this routine in the application things still don't seem to be setup correctly. Some other missing component ???? - threads seem to get created but their start proc never gets executed - scheduling... - signals aren't reliable Of course the later two problems could hinge on the first. -Steve ---------------------------------- E-Mail: Steve Tarkalson Date: 03/18/97 Time: 16:07:57 This message was sent by XF-Mail ---------------------------------- -------------End of forwarding message-------------------------