Ichthyostega
21fdce0dfc
Static initialisation and shutdown can be intricate; but in fact they work quite precise and deterministic, once you understand the rules of the game. In the actual case at hand the ClassLock was already destroyed, and it must be destroyed at that point, according to the standard. Simply because it is created on-demand, *after* the initialisation of the static DependencyFactory, which uses this lock, and so its destructor must be called befor the dtor of DependencyFactory -- which is precisely what happens. So there is no need to establish a special secure "base runtime system", and this whole idea is ill-guided. I'll thus close ticket #1133 as wontfix Conflicts: src/lib/dependable-base.hpp |
||
|---|---|---|
| .. | ||
| application | ||
| architecture | ||
| backend | ||
| engine | ||
| gui | ||
| model | ||
| plugins | ||
| workflow | ||
| DIR_INFO | ||
| index.txt | ||