Re: [RFC] Block all async signals used by gdb when initializing Guile

[Eli Zaretskii]

> Date: Mon, 31 Aug 2015 22:05:59 -0700
> From: Doug Evans <address@hidden>
> Cc: Mark Kettenis <address@hidden>, 
>       "address@hidden" <address@hidden>, guile-devel <address@hidden>
> 
> On Sat, Aug 29, 2015 at 7:37 PM, Eli Zaretskii <address@hidden> wrote:
> >> Date: Sat, 29 Aug 2015 23:04:02 +0200 (CEST)
> >> From: Mark Kettenis <address@hidden>
> >> CC: address@hidden, address@hidden, address@hidden
> >>
> >> 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?