The build machine is a core2 duo running 32-bit Centos 6.6 and custom kernel 3.10.
I recompiled the app using --march=native and --march=pentiumpro, but got the same error. I'll try the SIGKILL handler now. Danny > vex x86->IR: unhandled instruction bytes: 0xC5 0xF9 0x6E 0x45 > ==29426== valgrind: Unrecognised instruction at address 0x406ae5a. > ==29426== at 0x406AE5A: > std::tr1::__detail::_Prime_rehash_policy::_M_next_bkt(unsigned int) const > (hashtable_policy.h:460) > ==29426== by 0x4353724: std::tr1::_Hashtable<DvDbDataBaseObject*, > DvDbDataBaseObject*, std::allocator<DvDbDataBaseObject*>, > std::_Identity<DvDbDataBaseObject*>, equalp<DvDbDataBaseObject>, > DvDbDataBaseObject::Hash, std::tr1::__detail::_Mod_range_hashing, > std::tr1::__detail::_Default_ranged_hash, > std::tr1::__detail::_Prime_rehash_policy, false, true, > true>::_Hashtable(unsigned int, DvDbDataBaseObject::Hash const&, > std::tr1::__detail::_Mod_range_hashing const&, > std::tr1::__detail::_Default_ranged_hash const&, equalp<DvDbDataBaseObject> > const&, std::_Identity<DvDbDa On 27/11/2016, at 4:29 PM, Tom Hughes wrote: > Yes compiling with a different CPU target is the other option, but as you say > you may need to do the libraries as well. > > If you're using standard distro then it's likely the system libraries are OK > already though as a distro will compile for a fairly basic processor to get > maximum compatibility. It's only if you're using gentoo or something that > build from source that you might have an issue. > > Don't forget that a lot of libstdc++ is templates that will actually compile > as part of your program... > > Tom
------------------------------------------------------------------------------
_______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
