On 26/11/13 08:25, Joël Krähemann wrote: > I'm using g_atomic_int_set, g_atomic_int_get, g_atomic_int_xor and > g_atomic_int_and to implement thread synchronization. Could theses > functions be the problem or aren't they working proper?
No, it's not any of those. It's the low level locking in the C library. > Without running my application within valgrind I get the following out > of GDB. > > ***MEMORY-ERROR***: ags[14888]: GSlice: assertion failed: sinfo->n_allocated > > 0 That's just a bug of some sort in your program - valgrind may well help you find it if it was working for yuo. > Is this abort caused by XABORT? I don't know much about CPU instructions > because I normally just do C and I expect that everything just works > fine. It's caused by the C library trying to execute an XABORT instruction. > By the way in what bugzilla should I file that bug. On valgrind.org or > maybe on fedoraproject.org? I'm using fedora 20-beta. Oh if it's Fedora then the C library must be doing feature detection to enable the TM support. It's definitely an upstream bug so, the valgrind tracker is fine. Mark is the Fedora maintainer for valgrind anyway so he's aware of this and I'm guessing will patch in XABORT support once we have it. Sounds like it should be simple. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ------------------------------------------------------------------------------ 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
