That stack trace is native, not Python.
Something in libexempi.so.3 has tried to free a block of memory that isn't currently allocated. PSIR_FileWriter::DeleteExistingInfo()
calls std::_Rb_tree<unsigned short, std::pair<unsigned short const, PSIR_FileWriter::InternalRsrcInfo>…>::_M_erase(…)
, which I'm guessing means that PSIR_FileWriter
is trying to remove an element from a std::map<unsigned short, PSIR_FileWriter::InternalRsrcInfo>
.
In any event, libexempi has crashed your process. You may have to take it up with the libexempi developers.
Helpful hint: You can figure out what those gobbledegook symbols mean, e.g.:
_ZNSt8_Rb_treeItSt4pairIKtN15PSIR_FileWriter16InternalRsrcInfoEESt10_Select1stIS4_ESt4lessItESaIS4_EE8_M_eraseEPSt13_Rb_tree_nodeIS4_E
_ZN15PSIR_FileWriter18DeleteExistingInfoEv
…by running c++filt and pasting the stack trace into it.