public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/17247] gdb freezes on multi threaded app (test-case attached) Date: Wed, 10 Sep 2014 04:47:00 -0000 [thread overview] Message-ID: <bug-17247-4717-jKTJHOaW4T@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17247-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17247 --- Comment #40 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch, gdb-7.8-branch has been updated via 0df33300929f9b54ddcf040f9b1fe69c1a88304b (commit) from 0fefcb3282480d15a66fbf5daf65ef25adee9e76 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0df33300929f9b54ddcf040f9b1fe69c1a88304b commit 0df33300929f9b54ddcf040f9b1fe69c1a88304b Author: Doug Evans <xdje42@gmail.com> Date: Tue Sep 9 21:42:20 2014 -0700 Fix for PR 17247: Block SIGCHLD while initializing Guile. The problem here is that if a thread other than gdb's main thread gets a SIGCHLD (it's an asynchronous signal so the kernel will essentially pick a random thread) then gdb will hang if it is in sigsuspend when the SIGCHLD is delivered. The other thread will see the signal and the sigsuspend won't "wake up". Guile and libgc should be blocking SIGCHLD in their threads, but we need to work with Guile 2.0 and libgc 7.4. The problem first shows up in libgc 7.4 because it is the first release that enables multiple marker threads by default. gdb/ChangeLog: PR 17247 * guile.c: #include <signal.h>. (_initialize_guile): Block SIGCHLD while initializing Guile. Replaces the following, which is reverted. 2014-07-26 Doug Evans <xdje42@gmail.com> PR 17185 * configure.ac: Add check for header gc/gc.h. Add check for function setenv. * configure: Regenerate. * config.in: Regenerate. * guile/guile.c (_initialize_guile): Add workaround for libgc 7.4.0. ----------------------------------------------------------------------- Summary of changes: gdb/ChangeLog | 17 +++++++++++++ gdb/config.in | 6 ---- gdb/configure | 26 -------------------- gdb/configure.ac | 5 ---- gdb/guile/guile.c | 67 ++++++++++++++++++++++++++++------------------------ 5 files changed, 53 insertions(+), 68 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-09-10 4:47 UTC|newest] Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-09 13:35 [Bug gdb/17247] New: " glibc at iamsergio dot de 2014-08-09 20:26 ` [Bug gdb/17247] " mail at milianw dot de 2014-08-09 20:28 ` mail at milianw dot de 2014-08-10 0:54 ` philip.rebohle@tu-dortmund.de 2014-08-11 6:18 ` xdje42 at gmail dot com 2014-08-11 10:12 ` mail at milianw dot de 2014-08-12 8:43 ` kugel at rockbox dot org 2014-08-16 21:39 ` ideasman42 at gmail dot com 2014-08-17 2:47 ` net147 at gmail dot com 2014-08-18 14:14 ` rggjan at gmail dot com 2014-08-18 22:17 ` dje at google dot com 2014-08-18 23:10 ` dje at google dot com 2014-08-21 9:34 ` nimajnebwild at gmail dot com 2014-08-23 13:26 ` bernd.amend at gmail dot com 2014-08-23 16:07 ` dje at google dot com 2014-08-23 16:19 ` bernd.amend at gmail dot com 2014-08-23 21:11 ` kugel at rockbox dot org 2014-08-23 21:28 ` philip.rebohle@tu-dortmund.de 2014-08-23 21:37 ` xdje42 at gmail dot com 2014-08-23 21:39 ` xdje42 at gmail dot com 2014-08-23 21:42 ` kugel at rockbox dot org 2014-08-23 21:59 ` xdje42 at gmail dot com 2014-08-23 22:13 ` xdje42 at gmail dot com 2014-08-23 22:22 ` xdje42 at gmail dot com 2014-08-23 22:51 ` philip.rebohle@tu-dortmund.de 2014-08-23 22:56 ` philip.rebohle@tu-dortmund.de 2014-08-23 23:07 ` xdje42 at gmail dot com 2014-08-24 3:41 ` bernd.amend at gmail dot com 2014-08-24 11:40 ` mail at milianw dot de 2014-08-25 13:02 ` chenmulong at gmail dot com 2014-08-25 17:30 ` evgeny.grablyk at gmail dot com 2014-08-25 17:34 ` evgeny.grablyk at gmail dot com 2014-08-26 7:57 ` xdje42 at gmail dot com 2014-08-28 5:50 ` xdje42 at gmail dot com 2014-08-28 5:51 ` xdje42 at gmail dot com 2014-08-28 5:52 ` xdje42 at gmail dot com 2014-08-28 5:53 ` xdje42 at gmail dot com 2014-08-28 8:28 ` palves at redhat dot com 2014-08-28 10:53 ` corinna at vinschen dot de 2014-08-28 11:52 ` jaap at jcz dot nl 2014-08-29 20:43 ` evgeny.grablyk at gmail dot com 2014-08-31 0:41 ` xdje42 at gmail dot com 2014-08-31 17:27 ` xdje42 at gmail dot com 2014-08-31 18:58 ` rosslagerwall at gmail dot com 2014-09-01 13:44 ` corinna at vinschen dot de 2014-09-09 5:50 ` cvs-commit at gcc dot gnu.org 2014-09-10 4:47 ` cvs-commit at gcc dot gnu.org [this message] 2014-09-11 15:59 ` xdje42 at gmail dot com 2014-09-11 18:29 ` kbrown at cornell dot edu 2014-10-29 19:48 ` cvs-commit at gcc dot gnu.org 2021-09-28 2:45 ` dianeBerlusconi at gmail dot com 2021-10-21 6:54 ` bap.fayol at gmail dot com 2021-10-25 8:57 ` jameszen29 at gmail dot com 2021-10-25 9:14 ` nimajnebwild at gmail dot com
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-17247-4717-jKTJHOaW4T@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: linkBe 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).