Is this a case of two threads running the init table or an application thread running and using a global object before running the init table is complete?
Constructor order is another problem but I didn't think that had anything to do with this case. --Joel Stephen Tether <tet...@slac.stanford.edu> wrote: On 10/22/13 5:36 PM, Ralf Corsepius wrote: > Are sure not to be hit by > http://www.parashift.com/c++-faq/static-init-order.html ? An infamous C++ gotcha! No, it's clearly a case of the wrong ordering of constructor vs. member function calls for the *same* object instance. We recorded the value of the global timer, the object address and sundry other info for both constructor and member function calls. Thanks, guys, for your responses. - Steve _______________________________________________ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel _______________________________________________ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
