This is the mail archive of the
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: Eli Zaretskii <eliz at gnu dot org>
- Cc: gdb-patches at sourceware dot org, guile-devel at gnu dot org
- Date: Mon, 01 Sep 2014 18:18:45 +0200
- 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>
Eli Zaretskii <email@example.com> skribis:
>> From: firstname.lastname@example.org (Ludovic CourtÃs)
>> Date: Mon, 01 Sep 2014 12:11:19 +0200
>> Cc: email@example.com
>> Eli Zaretskii <firstname.lastname@example.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.
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.