History log of /external/valgrind/drd/tests/thread_name.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
22d2c784ef5d0732648e1c00e2bd3a5b63f8095c 26-Jul-2014 florian <florian@a5019735-40e9-0310-863c-91ae7b9d1cf9> Adapt testcase so it can be compiled with GCC 3.4.6 against glibc 2.3.4


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14193 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/drd/tests/thread_name.c
0652432e03b6e48dfe53d273c616eb3a347f34f8 07-Mar-2014 bart <bart@a5019735-40e9-0310-863c-91ae7b9d1cf9> drd/tests/thread_namedrd/tests/thread_name: Ensure mutex address uniqueness (see also #331847)

From: Ivo Raisr <ivosh@ivosh.net>


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13854 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/drd/tests/thread_name.c
d45d99553c15a361bb797d21ec6afb9bad22d2d4 31-May-2009 bart <bart@a5019735-40e9-0310-863c-91ae7b9d1cf9> - Added support for most of the ANNOTATE_...() macro's supported by
ThreadSanitizer.
- Modified DRD's error reporting code such that it does no longer let
the Valgrind core print the Valgrind thread ID but that it now prints
the DRD thread ID and name. Updated expected output files where
necessary.
- Modified drd/test/Makefile.am such that the tests using gcc's built-in
functions for atomic memory access such that these are only compiled when
the gcc version in use supports these built-in functions.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10186 a5019735-40e9-0310-863c-91ae7b9d1cf9
/external/valgrind/drd/tests/thread_name.c