From owner-freebsd-current Thu Jan 4 20:29:39 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 20:29:37 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 253FC37B400 for ; Thu, 4 Jan 2001 20:29:37 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f054SF532766 for ; Fri, 5 Jan 2001 00:28:15 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 5 Jan 2001 00:28:15 -0400 (AST) From: The Hermit Hacker To: Subject: using -pthread causes mcopidl to seg fault ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG morning all ... running 5.0-CURRENT here, and found the other day that mcopidl started to segfault the other day in kdelibs (from CVS) ... this evening, someone brought up the possibility that its a threading issue, and suggested taking -pthread out of the compile to see if it fixes it ... it did. are there any known problems with -pthread in 5.0-CURRENT right now? anything I can do to debug it (a gdb trace of the core file shows zip) ... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message