Re: [Valgrind-developers] helgrind: understanding race reports

[Julian S. <js...@ac...>]

> First is easy if we know the address to trace (with --trace-addr)
> before we start Helgrind. But we usually don't. :(

Would this help?

Once an address is marked as SHVAL_Race, start collecting more info
about it.  In particular, record stack traces for the next N (say 100)
memory accesses to it, or maybe better a stack trace for the first access
to it from each different thread.  Or some variant of these.

This doesn't help find the first access to an address in a race.  But
on the assumption that most races happen > 1 time (as reported in the
Rodehoffer "Racetrack" paper) then this might be an easy way to find
some other places where the address is accessed.

J