Re: crash in __static_initialization_and_destruction on 10.3.9 but not 10.4.4?
Re: crash in __static_initialization_and_destruction on 10.3.9 but not 10.4.4?
- Subject: Re: crash in __static_initialization_and_destruction on 10.3.9 but not 10.4.4?
- From: "John C. Daub" <email@hidden>
- Date: Tue, 31 Jan 2006 19:50:36 -0600
- Thread-topic: crash in __static_initialization_and_destruction on 10.3.9 but not 10.4.4?
on 1/31/06 5:00 PM, Steve Checkoway at email@hidden wrote:
> Since you're crashing in a static dtor, my guess would be that you
> have code that depends on the order of destruction. C++ offers no
> guarantees as to the order that destructors will be called. In
> particular, the order might have changed between OS releases or the
> order in which the linker links the files:
Y'know, that's distinctly possible. The code in question is the QpThread
library, a 3rd party C++ pthread wrapper (Google it, if you're curious).
There are a couple qpthr::QpCond globals (the object being destructed,
according to the backtrace), and they are initialized by other global
objects! So yes, this may well be the problem.
I know order of static initialization/destruction isn't guaranteed, but I've
been so focused on other possible causes that this didn't even cross my mind
*blush* I'll head down this route in the morning and see how it goes.
Thanx for the suggestion! :-)
--
John C. Daub }:-)>=
<mailto:email@hidden> <http://www.hsoi.com/>
"When there is no desire, all things are at peace." -- Tao Te Ching #30
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden