This is the mail archive of the
gdb-patches@sourceware.org
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: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- Cc: xdje42 at gmail dot com, gdb-patches at sourceware dot org, guile-devel at gnu dot org
- Date: Sun, 30 Aug 2015 05:37:19 +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>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sat, 29 Aug 2015 23:04:02 +0200 (CEST)
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> CC: eliz@gnu.org, gdb-patches@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 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.