Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: fhsueh at roku dot com
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org
Target Milestone: ---
On systems with slower
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91115
--- Comment #7 from Fred Hsueh ---
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/sanit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91115
--- Comment #6 from Fred Hsueh ---
Sorry for the long silence ... more on this:
I tracked down where the std::thread() that was causing this issue.
It seems that there are many similar long running tasks that needs to be
completed so we keep a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91115
--- Comment #3 from Fred Hsueh ---
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.
Any tips
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91115
--- Comment #1 from Fred Hsueh ---
Created attachment 46580
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46580&action=edit
Fixup memory location of shadow
This shadow location works better than the 32-bit default.
Severity: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: fhsueh at roku dot com
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org
