https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64478
Bernd Edlinger <bernd.edlinger at hotmail dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #3 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
(In reply to Andrew Pinski from comment #2)
> I think in this case tsan is incorrect, as the signal handler never returns.
> This is how C++ exceptions work with non-call signals also.
I dont think so.
Because the exception could happen also because of stack overflow
or simply asynchronos.
for instance ga stack overflow in malloc.
or a kill -SIGILL while executing malloc.
that will deadlock then in the signal handler.
