This is the mail archive of the
mailing list for the GDB project.
Re: [RFC] Block all async signals used by gdb when initializing Guile
- From: Doug Evans <xdje42 at gmail dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Mark Kettenis <mark dot kettenis at xs4all dot nl>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>, guile-devel <guile-devel at gnu dot org>
- Date: Tue, 1 Sep 2015 08:22:44 -0700
- Subject: Re: [RFC] Block all async signals used by gdb when initializing Guile
- Authentication-results: sourceware.org; auth=none
- References: <m3r3mmdn7g dot fsf at sspiff dot org> <831tel3o68 dot fsf at gnu dot org> <CAP9bCMQmWmbLg9qZ3ZyVyTF=fBOB-sJtFAr1=OCC_g53aGYRUw at mail dot gmail dot com> <83wpwd26lt dot fsf at gnu dot org> <CAP9bCMRh+y4aNzgOThff5syzGs5-i2XpcbLVYw5G1avgd4QVvA at mail dot gmail dot com> <201508292104 dot t7TL42OS020892 at glazunov dot sibelius dot xs4all dot nl> <83si711oyo dot fsf at gnu dot org> <CAP9bCMSC3-NKPptfdisum8Au50yF_LbFb9e2sP6jfGxNPOZSDA at mail dot gmail dot com> <83lhcqcin7 dot fsf at gnu dot org>
On Tue, Sep 1, 2015 at 7:35 AM, Eli Zaretskii <email@example.com> wrote:
>> The goal here is to block these signals from being sent to the threads
>> that Guile (or more specifically libgc) creates.
> Why only libgc? Don't we want to block these signals in any Guile
> code invoked later by GDB?
Any threads created later are required to DTRT themselves.
[Same as on python.]