Re: [Valgrind-users] Uninitialized access findings on non-static file scope variables that's been initialized?

[Dan K. <da...@ke...>]

On Wed, Aug 12, 2015 at 12:58 PM, Jeffrey Walton <nol...@gm...> wrote:
> The C++ object that uses it is in another translation unit, and it has
> a init_pritority attribute.

File-scope or static C++ objects are the spawn of the devil.
There is no reliable or portable way to control initialization order,
even with init_priority,   See e.g.
http://stackoverflow.com/questions/3371968/attribute-init-priorityx-in-gcc
- Dan