Re: SIGSEGV from qwt3diodummy constructor

[Micha B. <kri...@us...>]

> What was the reason for the problem?

The dummy object, any doubts ... :->
My guess:

We have a chain:

app -> qwtplot3d.dll/so -> qt.dll/so

Qt has to initialize some of its structures (QString ?). The
construction for the qwt3d static object happens too early. Perhaps the
qt shared library isn't full available/initialized at this point yet.
Similar for destruction. I don't know and seeing the topic-relevant
discussions in the net, I have to admit that I'm not even eager to know
why ... .
Anyway, in order to circumvent the problem, I moved all needed static
stuff inside functions (it's a common pattern). So whatever will be used
is constructed first in place when the function is called for the first
time. Because main runs then, order of initialization issues shouldn't
be longer an issue.

Micha  
--