This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH][PR guile/17247] Block SIGCHLD while initializing Guile


Eli Zaretskii <eliz@gnu.org> skribis:

>> 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.

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.

Ludoâ.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]