Re: problem with exiting from a Glib::Thread
- From: Chris Vine <chris cvine freeserve co uk>
- To: gtkmm-list gnome org
- Cc:
- Subject: Re: problem with exiting from a Glib::Thread
- Date: Sun, 26 Jun 2005 10:40:04 +0100
On Sunday 26 June 2005 07:56, Yair Hershkovitz wrote:
> i'm using mandriva 2005, they suppose to have nptl (there is a
> /usr/include/nptl with headers) but i dont know how to link againts it.
> i also don't know to which threads library glib is linked.
>
> how can i check that?
Glib uses whatever thread library is compiled into glibc if you either
compiled glib yourself or you are using the version of glib which comes with
your distribution. So the issue is really what thread library has been
compiled into glibc.
From what you say this is almost certainly NPTL, but you can check this by
doing:
/lib/libc.so.6 --version
The resulting text will include a line:
linuxthreads-0.10 by Xavier Leroy
if it uses linuxthreads, or a line:
NPTL 0.60 by Ulrich Drepper
(or a later version of NPTL) if it uses NPTL.
If it uses NPTL then try running your program with the following environmental
variable exported:
LD_ASSUME_KERNEL=2.4.19
In Redhat and Suse at least this forces NPTL to adopt Linuxthreads behaviour
(that is, it prevents forced stack unwinding) and it probably does the same
with your distribution, so if Glib::Thread::Exit works correctly with this
variable set and exported then you have a NPTL issue.
Chris
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]