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 17:39:29 +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>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: ludo@gnu.org (Ludovic CourtÃs)
> Date: Mon, 01 Sep 2014 12:11:19 +0200
> Cc: guile-devel@gnu.org
>
> Eli Zaretskii <eliz@gnu.org> skribis:
>
> > In GDB, Guile is just an extension language. I see no catastrophe in
> > saying there are some restrictions to what a Guile extension in GDB
> > can and cannot do.
>
> That can be acceptable, but requiring users to re-build Guile and GC
> without thread support is not, IMO.
Perhaps we should request GC and Guile to provide capabilities to
disable threads at run time, then.