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: Eli Zaretskii <eliz at gnu dot org>
- To: Doug Evans <xdje42 at gmail dot com>
- Cc: mark dot kettenis at xs4all dot nl, gdb-patches at sourceware dot org, guile-devel at gnu dot org
- Date: Tue, 01 Sep 2015 17:35:08 +0300
- 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>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Mon, 31 Aug 2015 22:05:59 -0700
> From: Doug Evans <email@example.com>
> Cc: Mark Kettenis <firstname.lastname@example.org>,
> "email@example.com" <firstname.lastname@example.org>, guile-devel <email@example.com>
> On Sat, Aug 29, 2015 at 7:37 PM, Eli Zaretskii <firstname.lastname@example.org> wrote:
> >> Date: Sat, 29 Aug 2015 23:04:02 +0200 (CEST)
> >> From: Mark Kettenis <email@example.com>
> >> CC: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
> >> I suppose blocking these in the threads that guile starts is necessary
> >> because that is the only way to guarantee that those signals will be
> >> delivered to the main gdb thread on POSIX systems.
> >> On Windows you probably need to do something completely different.
> > I might be missing something, because I don't see why.
> 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?
> Not sure how to do that on windows.
That problem doesn't exist on Windows, but what about Guile
application threads launched later?