From: Doug Evans <xdje42@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH][PR guile/17247] Block SIGCHLD while initializing Guile
Date: Wed, 10 Sep 2014 05:15:00 -0000 [thread overview]
Message-ID: <m3ha0grr8j.fsf@sspiff.org> (raw)
In-Reply-To: <m3wq9ds5ja.fsf@sspiff.org> (Doug Evans's message of "Mon, 08 Sep 2014 22:54:01 -0700")
Doug Evans <xdje42@gmail.com> writes:
> Doug Evans <xdje42@gmail.com> writes:
>> Hi.
>>
>> This patch fixes PR 17247.
>>
>> Basically, current Guile (git) starts an internal thread
>> (the "finalizer" thread), and libgc as of 7.4 now starts several
>> marker threads by default (before 7.4.0 one needed to configure
>> libgc with --enable-parallel-mark).
>>
>> When other threads are running, and they haven't blocked SIGCHLD,
>> then the kernel may send SIGCHLD to these threads, leaving gdb
>> hung in the sigsuspend calls in linux-nat.c.
>>
>> P.S. I have a tentative patch for PR 17314, which also fixes 17247,
>> but for a bit of robustness I'm applying both.
>>
>> 2014-08-31 Doug Evans <xdje42@gmail.com>
>>
>> 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.
>
> Hi.
> I have checked in this slight variation to trunk,
> and will commit it to the 7.8 branch tomorrow.
>
> [...]
> 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.
Pushed to 7.8 branch as well.
prev parent reply other threads:[~2014-09-10 5:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 19:08 Doug Evans
2014-08-31 19:36 ` Eli Zaretskii
2014-08-31 20:20 ` Doug Evans
2014-09-01 2:37 ` Eli Zaretskii
2014-09-01 10:11 ` Ludovic Courtès
2014-09-01 14:39 ` Eli Zaretskii
2014-09-01 16:18 ` Ludovic Courtès
2014-09-01 17:10 ` Eli Zaretskii
2014-09-01 22:04 ` Doug Evans
2014-09-02 15:25 ` Eli Zaretskii
2014-09-05 8:27 ` Doug Evans
2014-09-05 8:48 ` Eli Zaretskii
2014-09-05 10:51 ` Pedro Alves
2014-09-05 11:51 ` Eli Zaretskii
2014-09-05 12:48 ` Pedro Alves
2014-09-05 11:50 ` Ludovic Courtès
2014-09-01 12:48 ` Gary Benson
2014-09-01 16:35 ` Doug Evans
2014-09-09 5:54 ` Doug Evans
2014-09-10 5:15 ` Doug Evans [this message]
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=m3ha0grr8j.fsf@sspiff.org \
--to=xdje42@gmail.com \
--cc=gdb-patches@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