[Bug sanitizer/91115] stack-buffer-overflow on memset local variable when creating thread on ARM Linux

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91115

--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Fred Hsueh from comment #3)
> The actual SP and shadow byte location varies a bit between each run. Other
> than that, the signature looks very similar. Another thing to note is that
> the program has a high thread count, perhaps ~140.

That makes it very difficult to reproduce. Do you have any 2 runs that have the
'[f2]' shadow memory at the same location.

> 
> Any tips, preferences, or good starting points to look at for creating the
> testcase? I can't find any in ASAN or ARM related pre-existing cases.
> 
> thanks!

Is the reproducer an open-source software? I would somehow reduce # of threads.