public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/14382] gdb hangs after plotting with matplotlib
Date: Tue, 26 May 2015 08:29:00 -0000	[thread overview]
Message-ID: <bug-14382-4717-RwXGJDMTrN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14382-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=14382

--- Comment #14 from Pedro Alves <palves at redhat dot com> ---
(In reply to Tom Tromey from comment #13)
> I think if gdb uses signalfd to get SIGCHLD, and blocks it (what the
> man page says to do) then the various sigaction calls that libraries
> may do will just be ignored.

Ah, yes, but then the libraries were messing with SIGCHLD's sigaction because
they want to be notified of child exits, which would end up broken for them. 
Seems like a "what's the better breakage" decision case, and that may indeed be
better breakage.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-05-26  8:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-21 15:28 [Bug python/14382] New: " joeneeman at gmail dot com
2012-07-31 15:54 ` [Bug python/14382] " tromey at redhat dot com
2012-08-07  0:35 ` joeneeman at gmail dot com
2012-08-07  2:15 ` joeneeman at gmail dot com
2012-08-15 21:33 ` tromey at redhat dot com
2012-08-16 14:24 ` tromey at redhat dot com
2012-08-17  0:51 ` joeneeman at gmail dot com
2012-08-22 15:31 ` palves at redhat dot com
2012-08-22 16:58 ` tromey at redhat dot com
2013-03-07  9:16 ` m at bruenink dot de
2013-08-12 19:35 ` aegges at web dot de
2015-05-24 19:34 ` tromey at sourceware dot org
2015-05-25  8:36 ` palves at redhat dot com
2015-05-25  8:39 ` palves at redhat dot com
2015-05-25 20:52 ` tromey at sourceware dot org
2015-05-26  8:29 ` palves at redhat dot com [this message]
2015-05-26  8:56 ` palves at redhat dot com
2015-05-26  9:00 ` palves at redhat dot com
2015-05-26 10:26 ` palves at redhat dot com
2015-05-26 10:30 ` palves at redhat dot com
2015-05-26 10:32 ` palves at redhat dot com
2015-05-27  3:06 ` tromey at sourceware dot org
2015-05-27 16:36 ` xdje42 at gmail dot com
2015-05-27 18:37 ` palves at redhat dot com
2015-05-27 21:19 ` dje at google dot com
2015-05-28 11:45 ` palves at redhat dot com
2023-09-13 14:56 ` tromey at sourceware dot 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-14382-4717-RwXGJDMTrN@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).