Re: strange behaviour of library in static initialization context
From: Casper H.S. Dik (Casper.Dik_at_Sun.COM)
Date: 09/20/05
- Previous message: Dennis Lubert: "Re: strange behaviour of library in static initialization context"
- In reply to: Dennis Lubert: "Re: strange behaviour of library in static initialization context"
- Next in thread: Dennis Lubert: "Re: strange behaviour of library in static initialization context"
- Reply: Dennis Lubert: "Re: strange behaviour of library in static initialization context"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 20 Sep 2005 11:20:41 GMT
Dennis Lubert <plasmahh@tzi.de> writes:
>Do you mean the only Solaris implementation ? Our build system is running
>fine now onw different systems for over 2 years, it works this way (i.e.
>linking the library against libpthread, and not the main program) fine on
>Linux, FreeBSD, NetBSD and MacOSX, without any problems.
I mean the *only* system, not limited to Solaris.
But this might be limited to those cases were the thread library is loaded
as the result of a dlopen() later in the life of a process which is known
to be problematic except in those cases were main is threaded (or as in
Solaris 10 where a non-threaded process really is just a process
with a single thread)
Casper
-- Expressed in this posting are my opinions. They are in no way related to opinions held by my employer, Sun Microsystems. Statements on Sun products included here are not gospel and may be fiction rather than truth.
- Previous message: Dennis Lubert: "Re: strange behaviour of library in static initialization context"
- In reply to: Dennis Lubert: "Re: strange behaviour of library in static initialization context"
- Next in thread: Dennis Lubert: "Re: strange behaviour of library in static initialization context"
- Reply: Dennis Lubert: "Re: strange behaviour of library in static initialization context"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|