From owner-freebsd-stable Sun Mar 4 10: 5:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.org.ru (sweet.etrust.ru [194.84.67.5]) by hub.freebsd.org (Postfix) with ESMTP id A218037B718 for ; Sun, 4 Mar 2001 10:05:37 -0800 (PST) (envelope-from osa@freebsd.org.ru) Received: by freebsd.org.ru (Postfix, from userid 1000) id 0B16C161; Sun, 4 Mar 2001 21:05:33 +0300 (MSK) Date: Sun, 4 Mar 2001 21:05:33 +0300 From: "Sergey A. Osokin" To: stable@FreeBSD.org Subject: Re: gcc -pthread / segfault problem Message-ID: <20010304210532.A10589@freebsd.org.ru> Reply-To: osa@FreeBSD.org.ru References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from fjoe@newst.net on Sun, Mar 04, 2001 at 12:56:30AM +0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 04, 2001 at 12:56:30AM +0600, Max Khon wrote: > hi, there! > > On Fri, 2 Mar 2001, Lists Account wrote: > > > I was coding some stuff under a 4.2 box of mine here earlier today and I > > seem to have hit a very strange bug, I was wondering if anyone could help > > me out here. > > > > I wrote a bunch of pthread enabled code, when I tried to run the program, > > after I compiled it with -pthread (I had to with the threading code in > > there), it segfaulted, so I ran it through gdb, and it was segfaulting on > > malloc(). So I dug around some more, and eventually I tried changing that > > single line to a c++ new() call, no more problems... > > 4.2-RELEASE has known problems with C++ and pthreads > please upgrade to latest -STABLE latest means RELENG_4 after 06.01.2001 :-) Rgdz, /"\ Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN osa@freebsd.org.ru X AGAINST HTML MAIL http://freebsd.org.ru/~osa/ / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message