[RFC] Block all async signals used by gdb when initializing Guile
Eli Zaretskii
eliz@gnu.org
Tue Sep 1 15:50:00 GMT 2015
> Date: Tue, 1 Sep 2015 08:22:44 -0700
> From: Doug Evans <xdje42@gmail.com>
> Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
> "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>, guile-devel <guile-devel@gnu.org>
>
> On Tue, Sep 1, 2015 at 7:35 AM, Eli Zaretskii <eliz@gnu.org> 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.]
Then I guess this problem can be ignored for Windows.
More information about the Gdb-patches
mailing list