This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH][PR guile/17247] Block SIGCHLD while initializing Guile
- From: Eli Zaretskii <eliz at gnu dot org>
- To: ludo at gnu dot org (Ludovic CourtÃs)
- Cc: gdb-patches at sourceware dot org, guile-devel at gnu dot org
- Date: Mon, 01 Sep 2014 20:10:40 +0300
- Subject: Re: [PATCH][PR guile/17247] Block SIGCHLD while initializing Guile
- Authentication-results: sourceware.org; auth=none
- References: <m31trwv5o1 dot fsf at sspiff dot org> <834mwsh2nu dot fsf at gnu dot org> <CAP9bCMTNsoi6AhQxJtzjc6=o9iHi8TXkX32OiKbArAuAnsjZUQ at mail dot gmail dot com> <8338ccgj78 dot fsf at gnu dot org> <87ppffabw8 dot fsf at gnu dot org> <83y4u3flr2 dot fsf at gnu dot org> <87r3zv71qy dot fsf at gnu dot org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: ludo@gnu.org (Ludovic CourtÃs)
> Cc: gdb-patches@sourceware.org, guile-devel@gnu.org
> Date: Mon, 01 Sep 2014 18:18:45 +0200
>
> Eli Zaretskii <eliz@gnu.org> skribis:
>
> > Perhaps we should request GC and Guile to provide capabilities to
> > disable threads at run time, then.
>
> I donât think we need to go this far: reading the recent discussions, it
> seems Doug found a way to make sure Guileâs and libgcâs internal threads
> donât receive signals that GDB is interested in, which should be enough
> for practical purposes.
That's just the tip of an iceberg, I'm afraid.