Hi,

I'm running helgrind against our code base and see this report. I once again 
cannot include all the code due to its proprietary and disclosed nature.

Possible data race during write of size 8 at 0x58EEC60 by thread #1
Locks held: none
   at 0x4A87603: ...
   by 0xE818EB4: ...
   by 0xE816B04: ...
   by 0xE816ABE: ...
   by 0xDD80701: ...
   by 0xDD80701: ...
   by 0xDD1FF8C: ...
   by 0x42503E: ...
   by 0x4263B0: ...
   by 0x4267E6: ...
 Address 0x58eec60 is 160 bytes inside a block of size 408 alloc'd
   at 0x484BF58: operator new(unsigned long) (vg_replace_malloc.c:487)
   by 0xE816395: ...
   by 0xE8143DC: ...
   by 0xE8143DC: ...
   by 0x4A64C49: ...
   by 0xDD7427A: ...
   by 0xDD7E472: ...
   by 0xDD7E58E: ...
   by 0xDD1FF8C: ...
   by 0x42503E: ...
   by 0x4263B0: ...
   by 0x4267E6: ...
 Block was alloc'd by thread #1
I'm a bit confused as to how this can be a data race if there's only the main 
thread involved. Could this be a false positive or how do I read this report 
correctly?

Thanks,
Thomas

_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to