https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91115
--- Comment #7 from Fred Hsueh <fhsueh at roku dot com> --- This looks more like an odd interaction with ASAN and fork(). The process reporting the stack-buffer-overflow is actually a fork() child of the main process. Something similar to https://github.com/google/sanitizers/issues/836 "LeakSanitizer and AddressSanitizer detect false leaks after fork() with threads". Still working on a working demo, but it might be something like this: - Create thread #1 - Create thread #2 - thread #1 completes and cleans up. - fork() child: - create thread #3 (uses same spot as #1 ok!) - create thread #4 (uses same spot as #2 ... ASAN detects it writing memory in another thread's memory).
