From owner-freebsd-current Wed Nov 1 21:54: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id A0A4C37B4C5; Wed, 1 Nov 2000 21:53:50 -0800 (PST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id LAA64220; Thu, 2 Nov 2000 11:53:18 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 2 Nov 2000 11:53:17 +0600 (NS) From: Max Khon To: John Polstra Cc: current@FreeBSD.ORG, sobomax@FreeBSD.ORG, obrien@FreeBSD.ORG, deischen@FreeBSD.ORG Subject: Re: ABI is broken?? In-Reply-To: <200011011835.eA1IZl207585@vashon.polstra.com> 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 hi, there! On Wed, 1 Nov 2000, John Polstra wrote: > Here are all the random facts which, when put together, explain what > is going on. > > Your old application was (like all -pthread programs) linked > with "/usr/lib/libgcc_r.a". That library contains a function > "__register_frame_info" which uses some of the facilities of the > pthreads library "libc_r". > > The pthreads library has to be initialized before it can be used, by > a call to _thread_init. If some functions such as pthread_mutex_lock > are called before the library has been initialized, a segmentation > violation results. [...] > Overall I would lean toward putting the hack into pthread_mutex_lock. > Comments? do we still need uthread_autoinit.cc? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message