> Date: Tue, 1 Sep 2015 08:22:44 -0700
> From: Doug Evans
> Cc: Mark Kettenis ,
> "gdb-patc...@sourceware.org" , guile-devel
>
>
> On Tue, Sep 1, 2015 at 7:35 AM, Eli Zaretskii wrote:
> >> The goal here is to block these signals from being sent to the threads
> >> that Guile (or more sp
On Tue, Sep 1, 2015 at 7:35 AM, Eli Zaretskii 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 create
> Date: Mon, 31 Aug 2015 22:05:59 -0700
> From: Doug Evans
> Cc: Mark Kettenis ,
> "gdb-patc...@sourceware.org" , guile-devel
>
>
> On Sat, Aug 29, 2015 at 7:37 PM, Eli Zaretskii wrote:
> >> Date: Sat, 29 Aug 2015 23:04:02 +0200 (CEST)
> >> From: Mark Kettenis
> >> CC: e...@gnu.org, gd
On Sat, Aug 29, 2015 at 7:37 PM, Eli Zaretskii wrote:
>> 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 onl
> Date: Sat, 29 Aug 2015 13:39:55 -0700
> From: 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 sigpr
> 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
> 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
> >>
>
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
> 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
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
> 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
11 matches
Mail list logo
