Xeverous

`Segoe UI` string: - in UTF-8: `53 65 67 6F 65 20 55 49` - in UTF-16 BE: `0053 0065 0067 006f 0065 0020 0055 0049` - in UTF-16 LE:...

Another repro, more deterministic crash this way: ```cpp #include int main() { using namespace nana; paint::font f; } ``` output: ``` terminate called without an active exception ``` Looks like...

What are your build flags? (`-flto -fno-fat-lto-objects` must be given both to the compiler and the linger) Check that the linker is actually performing LTO - in my case I...

I don't use static standard libraries.

Great, at least you have a repro. I had very unstable undefined behaviour which was causing different stack traces and different memory corruptions on different machines. Any guess why this...

> Just thinking: what if you search for all the global objects created in the implementation and create one more global object to rule it all? This is a good...

I doubt that LTO would eliminate initialization of static class members. If so happens, this is a compiler bug. I will check dependencies between all static objects and: - whether...

This is not this issue. The bugs you linked end in linker errors (build fails) whereas in the case with nana the build succeeds and the executable crashes.

> The issue is caused by the side-effect of LTO. C++ defines clearly that static class members are initialized before `main()`, but it seems that LTO incorrectly eliminates the initialization...

It is. It is very friendly, it can remove binary bloat and make executables faster and tremedously smaller. I would rather say that `static` is the offender and has a...