On Mon, Nov 25, 2013 at 10:40:40PM +0000, Tom Hughes wrote: > On 25/11/13 22:06, Joël Krähemann wrote: > > > Hi, I get this nice error message out of valgrind while starting or > > using my application and I don't know why. > > > > http://sf.net/p/ags > > > > Please help. > > Given the location of the instruction I'm guessing you have a Haswell > processor and you've built glibc with transactional memory support so > that it is trying to do lock ellision using the transactional memory > instructions. > > The transactional memory instructions aren't fully supported in valgrind > yet, so you'll probably have to rebuild glibc without that support for now.
This is somewhat unfortunate. We do have prelimenary support, but only implemented xstart and xtest to indicate the transaction always immediately fails. The instruction hit is xabort, which in the valgrind case would always just be a NOP since no transaction is (can be) active. If there isn't a bug report for XABORT not being implemented, please do file one. We really should add it. Thanks, Mark ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
