Is this static init fiasco?

[ShubhaDorothy]

I have a global object 'obj' defined in a file x.cpp without any storage specifier. The object 'obj' is defined (constructor) in another dll.( statically linked dll). when i run the constructor of this file 'x' ( which is not a global object, but uses the 'obj' object ), i get an access violation inside the 'obj' dll?

i understand static oreder fiasco is relevant to two global objects, where one uses the other..

The access violation happens only in debug build.. should i worry about releasing this code?

Please do help me with this.
Shubha

[weaknessforcats]

So, if I get this right, you have:

 
MyClass obj;           //constructor in another file
 
void fx()
{
     AnotherClass  x(obj);
}
 

Is this right?

If so, the constructor for MyClass is called before main() starts. The global fiasco is when obj needs constructor arguments since those arguments may not have been created yet.

Assuming that's not the case, then an access violation trying to create object x most likely has to so with using a null, or uninitialized pointer in the MyClass constructor.

Perhaps a little code would clear this up.