From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-472100-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 5061 invoked by alias); 3 Jan 2015 08:37:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 5029 invoked by uid 48); 3 Jan 2015 08:36:54 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.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 08:37: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: bug_status resolution
Message-ID: <bug-64478-4-5RATspw3z0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64478-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64478-4@http.gcc.gnu.org/bugzilla/>
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/msg00094.txt.bz2

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