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: ludo at gnu dot org (Ludovic CourtÃs)
- To: gdb-patches at sourceware dot org
- Cc: guile-devel at gnu dot org
- Date: Mon, 01 Sep 2014 12:11:19 +0200
- Subject: Re: [PATCH][PR guile/17247] Block SIGCHLD while initializing Guile
- Authentication-results: sourceware.org; auth=none
- Followup-to: gmane.comp.gdb.patches
- 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>
Eli Zaretskii <eliz@gnu.org> skribis:
>> Date: Sun, 31 Aug 2014 13:20:48 -0700
>> From: Doug Evans <xdje42@gmail.com>
>> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>, guile-devel <guile-devel@gnu.org>
>>
>> Users are going to want to start threads.
>
> If users want threads in Guile, they can use Guile.
>
> 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.
Ludoâ.