From owner-freebsd-threads@FreeBSD.ORG Wed Oct 11 16:40:31 2006 Return-Path: X-Original-To: freebsd-threads@hub.freebsd.org Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F0E016A47B for ; Wed, 11 Oct 2006 16:40:31 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3F8B43D8F for ; Wed, 11 Oct 2006 16:40:20 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9BGeKuG081874 for ; Wed, 11 Oct 2006 16:40:20 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9BGeKSd081872; Wed, 11 Oct 2006 16:40:20 GMT (envelope-from gnats) Date: Wed, 11 Oct 2006 16:40:20 GMT Message-Id: <200610111640.k9BGeKSd081872@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: Daniel Eischen Cc: 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 Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 16:40:31 -0000 The following reply was made to PR threads/104297; it has been noted by GNATS. From: Daniel Eischen To: Gergely CZUCZY Cc: FreeBSD-gnats-submit@freebsd.org, freebsd-threads@freebsd.org Subject: Re: threads/104297: mixing libthr and libpthread through libs segfaults the binary Date: Wed, 11 Oct 2006 12:28:53 -0400 (EDT) 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