public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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 [thread overview]
Message-ID: <bug-64478-4-5RATspw3z0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64478-4@http.gcc.gnu.org/bugzilla/>
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
next prev parent reply other threads:[~2015-01-03 8:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-03 3:45 [Bug ada/64478] New: " bernd.edlinger at hotmail dot de
2015-01-03 3:46 ` [Bug ada/64478] " bernd.edlinger at hotmail dot de
2015-01-03 3:57 ` pinskia at gcc dot gnu.org
2015-01-03 7:34 ` bernd.edlinger at hotmail dot de
2015-01-03 7:36 ` pinskia at gcc dot gnu.org
2015-01-03 7:42 ` bernd.edlinger at hotmail dot de
2015-01-03 7:51 ` pinskia at gcc dot gnu.org
2015-01-03 8:20 ` bernd.edlinger at hotmail dot de
2015-01-03 8:37 ` pinskia at gcc dot gnu.org [this message]
2015-01-03 8:47 ` bernd.edlinger at hotmail dot de
2015-01-03 8:53 ` pinskia at gcc dot gnu.org
2015-01-03 9:20 ` bernd.edlinger at hotmail dot de
2015-01-03 11:11 ` bernd.edlinger at hotmail dot de
2015-01-04 10:03 ` ebotcazou at gcc dot gnu.org
2015-01-04 11:59 ` bernd.edlinger at hotmail dot de
2015-01-04 12:44 ` bernd.edlinger at hotmail dot de
2015-01-04 15:00 ` ebotcazou at gcc dot gnu.org
2015-01-04 15:26 ` bernd.edlinger at hotmail dot de
2015-01-13 8:58 ` bernd.edlinger at hotmail dot de
2015-01-13 9:31 ` ebotcazou at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-64478-4-5RATspw3z0@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).