Thanks for the reply, Julian. I indeed might have looked at an incomplete report. After having worked with helgrind a few more days things make more sense now.
Cheers, Thomas ________________________________ From: Julian Seward <jseward.t...@gmail.com> Sent: Friday, June 28, 2024 12:44 PM To: Thomas Wollenzin <wolle...@msn.com>; valgrind-users@lists.sourceforge.net <valgrind-users@lists.sourceforge.net> Subject: Re: [Valgrind-users] helgrind question regarding 'Possible data race during write of size 8' At least in the text you included, there's nothing that indicates what the the other thread/access is. We have: > Possible data race during write of size 8 at 0x58EEC60 by thread #1 > Locks held: none and these, but they just tell you about the data address involved in the race: > Address 0x58eec60 is 160 bytes inside a block of size 408 alloc'd > at 0x484BF58: operator new(unsigned long) (vg_replace_malloc.c:487) > Block was alloc'd by thread #1 There should be yet another stack which shows where the conflicting access in the "other" thread is. J
_______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
