Am Samstag, 27. Oktober 2007 schrieb Julian Seward: > > thanks for your work on a helgrind replacement. Such a tool is a great > > help for us. > > Thanks for the feedback and test program. What version of glibc do > your test machines have?
Both machines are opensuse 10.2 i386: GNU C Library stable release version 2.5 (20061011), by Roland McGrath et al. x86_64: GNU C Library stable release version 2.5 (20061011), by Roland McGrath et al. > > 1. The concurrent writes on line 72 are not protected by a mutex > > (uncommented above and below). Thrcheck does not flag this error on my > > i386 and x86_64 machines. > > This appears to be scheduling-sensitive. For both i386 and x86_64 (Core 2 > Duo) I get an error here maybe for every 1 run in 4: You are right. After running the test program several times I also see the error here. > > 3. The x86_64 version only shows that one thread is started. Threads 3 -- > > 9 are not shown. > > I presume you mean you only get one message of the form > > Thread #3 was created > at 0x586748E: clone (in /lib64/libc-2.5.so) > by 0x4E2F305: do_clone (in /lib64/libpthread-2.5.so) > by 0x4E2F7C5: pthread_create@@GLIBC_2.2.5 (in > /lib64/libpthread-2.5.so) by 0x4C23864: [EMAIL PROTECTED] > (tc_intercepts.c:190) > > These message are not printed when a thread starts - that would be > impractical for a program with many threads. They are printed on demand > so as to make later error messages make sense. Specifically, if it > produces a race message containing this: > > Possible data race during [...] > Old state: shared-readonly by threads #3, #6 > New state: shared-modified by threads #3, #6 > > then it will first print out a "Thread #3 was created at" message, and a > "Thread #6 was created at" message, so you can make sense of the race > message. Ok, now I understand that the number of messages varies between different runs. Is there some documentation on the algorithm that thrcheck uses? Greetings Christoph ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Valgrind-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
