From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21352 invoked by alias); 3 Jan 2015 07:51:37 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 21316 invoked by uid 48); 3 Jan 2015 07:51:32 -0000 From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/64478] Ada Exception handlers call signal-unsafe malloc/free Date: Sat, 03 Jan 2015 07:51:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ada X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-01/txt/msg00090.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64478 --- Comment #6 from Andrew Pinski --- (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.