Funny, I have an unsolved bug sort of in this area that I have never managed to reproduce. (I don't use C++ normally so that may hinder my efforts a bit? I'll t

Funny, I have an unsolved bug sort of in this area that I have never managed to reproduce. (I don't use C++ normally so that may hinder my efforts a bit? I'll try and read the article to see if that helps a bit.) I have exactly one core dump from a colleague who managed to reproduce the issue once after thousands of power cycles, and never again even after doing another 100,000 power cycles. The core file indicates that in a library opened using dlopen(), in a chunk of memory that contains various static variables that would have to be set to 0 according to spec, are instead set to weird values, causing a deadlock. Everything should be initialized in the correct order and there is no threading yet at that point. I have not managed to identify any sources of randomness (inside the program). Asking gdb to break when something touches these variables doesn't show up anything. Etc. With just one core file and no access to the customer's production environment we decided to just restart the program if it deadlocks...