https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64478
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Bernd Edlinger from comment #5) > but I cant see why a potential deadlock in an exception > handler is not a bug? 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.
