From owner-freebsd-threads@FreeBSD.ORG Wed Oct 11 16:30:23 2006 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E3E616A5EA; Wed, 11 Oct 2006 16:30:23 +0000 (UTC) (envelope-from eischen@vigrid.com) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5A2943E37; Wed, 11 Oct 2006 16:28:54 +0000 (GMT) (envelope-from eischen@vigrid.com) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.7/8.13.7/NETPLEX) with ESMTP id k9BGSrMu006547; Wed, 11 Oct 2006 12:28:53 -0400 (EDT) Date: Wed, 11 Oct 2006 12:28:53 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Gergely CZUCZY In-Reply-To: <20061011161414.GA49235@harmless.hu> Message-ID: References: <200610111429.k9BET3aF047135@marvin.harmless.hu> <20061011161414.GA49235@harmless.hu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-2.0.2 (mail.ntplx.net [204.213.176.10]); Wed, 11 Oct 2006 12:28:53 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: FreeBSD-gnats-submit@freebsd.org, freebsd-threads@freebsd.org Subject: Re: threads/104297: mixing libthr and libpthread through libs segfaults the binary X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 16:30:23 -0000 On Wed, 11 Oct 2006, Gergely CZUCZY wrote: > On Wed, Oct 11, 2006 at 12:12:32PM -0400, Daniel Eischen wrote: >> On Wed, 11 Oct 2006, Gergely CZUCZY wrote: >> >>> >>>> Number: 104297 >>>> Category: threads >>>> Synopsis: mixing libthr and libpthread through libs segfaults the binary >> >> Of course it does, and that's to be expected. This is not >> a bug. > it see. then why can pthread and libc_r be mixed? They can't and it isn't supported. > and how do i use libthr if one of the libs i link against > is using libpthread? You can't unless you relink everything or you use libmap.conf(5). -- DE