https://bugs.kde.org/show_bug.cgi?id=444488
--- Comment #5 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Paul Floyd from comment #4) > Thanks for adding me to the CC Philippe. > > If I do this: > export GLIBC_TUNABLES="glibc.pthread.stack_cache_size=0" > > Then helgrind/tests/tls_threads fails with just > +--21937:0: sched WARNING: pthread stack cache cannot be disabled! > > Without the env var there are a load of > > +Possible data race during write of size 8 at 0x........ by thread #x > > errors > > Do we have a way of knowing that GLIBC_TUNABLES did something so that we > don't need to twiddle with stack_cache_actsize? If we can detect the glibc version, then we can avoid using the old stack_cache_actsize hack. > Also --sim-hints=no-nptl-pthread-stackcache isn't turned on by default. Do > we want to check for it in setup_client_env () and only put GLIBC_TUNABLES > in the environment if it is used? Or perhaps add a new simhint. I think we should check and use the existing hint. Current users of the hint will/should have the same behaviour whatever the glibc version. > > Bonus points for handling GLIBC_TUNABLES already set by the tuner, and add > or replace glibc.pthread.stack_cache_size > > This doesn't seem to help the example being discussed in the valgrind-users > list. -- You are receiving this mail because: You are watching all bug changes.
