public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bernd.edlinger at hotmail dot de" <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:47:00 -0000	[thread overview]
Message-ID: <bug-64478-4-QkyoYoZxBr@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

--- Comment #9 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
Sorry, Andrew,

a deadlock in the Ada exception handler is an Ada BUG
by definition.

Even if YOU can't fix it easily.

The memory could be pre-allocated as the call stack
and we should make it to the point where the user code
starts.  If they call malloc then that's no more our
problem.

Please stop this now.

I still dont see what's wrong with tsan here, the signal could
easily be from a kill -SIGSEGV .

Thanks
Bernd.


  parent reply	other threads:[~2015-01-03  8:47 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
2015-01-03  8:47 ` bernd.edlinger at hotmail dot de [this message]
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-QkyoYoZxBr@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).