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

2015-08-29 Thread Eli Zaretskii
> Date: Sat, 29 Aug 2015 23:04:02 +0200 (CEST) > From: Mark Kettenis > CC: e...@gnu.org, gdb-patc...@sourceware.org, guile-devel@gnu.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

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

2015-08-29 Thread Eli Zaretskii
> Date: Sat, 29 Aug 2015 13:39:55 -0700 > From: Doug Evans > Cc: "gdb-patc...@sourceware.org" , guile-devel > > > On Sat, Aug 29, 2015 at 1:16 PM, Eli Zaretskii wrote: > >> Date: Sat, 29 Aug 2015 12:20:24 -0700 > >> From: Doug Evans > >> Cc: "gdb-patc...@sourceware.org" , guile-devel > >> >

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

2015-08-29 Thread Doug Evans
On Sat, Aug 29, 2015 at 1:16 PM, Eli Zaretskii wrote: >> Date: Sat, 29 Aug 2015 12:20:24 -0700 >> From: Doug Evans >> Cc: "gdb-patc...@sourceware.org" , guile-devel >> >> >> > What about platforms that don't have sigprocmask, but do have SIGINT? >> > Don't we want to block SIGINT on those platf

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

2015-08-29 Thread Eli Zaretskii
> Date: Sat, 29 Aug 2015 12:20:24 -0700 > From: Doug Evans > Cc: "gdb-patc...@sourceware.org" , guile-devel > > > > What about platforms that don't have sigprocmask, but do have SIGINT? > > Don't we want to block SIGINT on those platforms? > > Do they have threads They might. (The only way I

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

2015-08-29 Thread Doug Evans
On Sat, Aug 29, 2015 at 12:11 PM, Eli Zaretskii wrote: >> From: Doug Evans >> cc: guile-devel@gnu.org >> Date: Sat, 29 Aug 2015 10:22:11 -0700 >> >> --- a/gdb/guile/guile.c >> +++ b/gdb/guile/guile.c >> @@ -847,7 +847,7 @@ _initialize_guile (void) >> #if HAVE_GUILE >>{ >> #ifdef HAVE_SIGPRO

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

2015-08-29 Thread Eli Zaretskii
> From: Doug Evans > cc: guile-devel@gnu.org > Date: Sat, 29 Aug 2015 10:22:11 -0700 > > --- a/gdb/guile/guile.c > +++ b/gdb/guile/guile.c > @@ -847,7 +847,7 @@ _initialize_guile (void) > #if HAVE_GUILE >{ > #ifdef HAVE_SIGPROCMASK > -sigset_t sigchld_mask, prev_mask; > +sigset_t gu

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

2015-08-29 Thread Doug Evans
Hi. When Guile initializes it will start several GC threads (libgc). It's important that these threads block SIGCHLD (PR 17247). This patch extends this to all async signals used by gdb. One improvement on this patch would be to have event-top.c (or some such) provide a routine that calls sigadd