Date: Thu, 2 Nov 2000 11:53:17 +0600 (NS) From: Max Khon <fjoe@iclub.nsu.ru> To: John Polstra <jdp@polstra.com> Cc: current@FreeBSD.ORG, sobomax@FreeBSD.ORG, obrien@FreeBSD.ORG, deischen@FreeBSD.ORG Subject: Re: ABI is broken?? Message-ID: <Pine.BSF.4.21.0011021152050.62602-100000@iclub.nsu.ru> In-Reply-To: <200011011835.eA1IZl207585@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0011021152050.62602-100000>