title: Segmentation fault when logging using spdlog in an app that includes another spdlog
body: <p>I have a native library that uses <code>spdlog</code> for internal logging.</p>
  <p>The library is compiled as shared library and the results <code>.so</code> files are then used in an Android project which has its own JNI and native c++ code which also uses <code>spdlog</code>.</p>
  <p>The first time a call to <code>spdlog</code> is made, we experience a <code>SIGSEGV</code> from it. After some research we found that since <code>spdlog</code> is a header-only library it may cause issues when using it this way, so we changed to using it as a static library inside the native library.</p>
  <p>This seems to solve the issue but now we get the <code>SIGSEGV</code> on the first call to <code>spdlog</code> from the application's native code.</p>
  <p>Are there any limitations or issues with using <code>spdlog</code> this way, specifically in an Android project?
  Any suggestions on debugging the issue?</p>
  <p>If any code can be helpful, let me know what is needed and I'll update the question</p>
  <p><strong>Edit</strong></p>
  <p>Also, it's worth noting that it only happens when the native library is built in Release mode. In Debug everything works as expected</p>