Boost C++ Libraries: Ticket #11427: Boost serialization error when used with Jarsigner https://svn.boost.org/trac10/ticket/11427 <p> Hello, </p> <p> Background: </p> <p> I order to automate signing Android APK file files, I have a Gemalto USB smart card plugged into a Scientific Linux 6.6 Virtual Machine. I've installed Boost (1_58) and the necessary software (Java OpenJDK 1.7.0_79) and libraries (pcsc-lite, etc) in order for the VM to recognise and read certs from the smart card. </p> <p> Even though Jarsigners signs the apk file, it always bombs out with this message: </p> <p> jarsigner: /usr/local/include/boost/serialization/singleton.hpp:131: static T&amp; boost::serialization::singleton&lt;T&gt;::get_instance() [with T = boost::archive::detail::oserializer&lt;boost::archive::text_oarchive, MiniDriver&gt;]: Assertion `! detail::singleton_wrapper&lt; T &gt;::m_is_destroyed' failed. Aborted </p> <p> This is the code I am running (most basic form): </p> <p> jarsigner -verbose -storetype PKCS11 -storepass 123456 $FILENAME Alias </p> <p> As mentioned before, the apk is actually signing file and I can verify the cert is loaded into the app successfully. However for better error handing and logging I need to resolve this boost error. </p> <p> Any advice would be greatly appreciated. </p> <p> Ben </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/11427 Trac 1.4.3 Robert Ramey Tue, 29 Sep 2015 22:15:41 GMT status changed; resolution set https://svn.boost.org/trac10/ticket/11427#comment:1 https://svn.boost.org/trac10/ticket/11427#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">invalid</span> </li> </ul> <p> Seems to me this would be an issue with the Jarsigner. This indicates that the static serialization DLL has not been freed before the end of the program. In any case, I don't see how I can address it. </p> <p> Also note that this double checking only occurs on debug build. It might be that the debug version of the dll is being used. </p> <p> in any case, I don't see what I can do here. </p> Ticket