https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64478
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Bernd Edlinger from comment #7)
> (In reply to Andrew Pinski from comment #6)
> > Actually here is what glibc says about malloc:
> > Function: void * malloc (size_t size)
> > Preliminary: | MT-Safe | AS-Unsafe lock | AC-Unsafe lock fd mem | See POSIX
> > Safety Concepts.
> >
> > But this is a non-Async-Signal here we are talking about so this is safe and
> > a bug in tsan for not realizing that.
>
> Well, in this example the signal is synchonous,
> but I see the same problem also when the stack overflows.
Stack overflow is still synchonous. But really there is not much to be done
with a stack overflow. it is hard for anything to do with both stack overflow
not in malloc and one in malloc unless you know you are not in malloc. Still
not a bug which is fixable easily.
Still a BUG in tsan for reporting a non bug. Please report this to TSAN for
reporting a non BUG.
Thanks,
Andrew Pinski
