From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: xdje42@gmail.com, gdb-patches@sourceware.org, guile-devel@gnu.org
Subject: Re: [RFC] Block all async signals used by gdb when initializing Guile
Date: Sun, 30 Aug 2015 02:42:00 -0000 [thread overview]
Message-ID: <83si711oyo.fsf@gnu.org> (raw)
In-Reply-To: <201508292104.t7TL42OS020892@glazunov.sibelius.xs4all.nl>
> 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.
next prev parent reply other threads:[~2015-08-30 2:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 17:23 Doug Evans
2015-08-29 19:11 ` Eli Zaretskii
2015-08-29 19:20 ` Doug Evans
2015-08-29 20:16 ` Eli Zaretskii
2015-08-29 20:40 ` Doug Evans
2015-08-29 21:04 ` Mark Kettenis
2015-08-30 2:42 ` Eli Zaretskii [this message]
2015-09-01 5:06 ` Doug Evans
2015-09-01 14:36 ` Eli Zaretskii
2015-09-01 15:22 ` Doug Evans
2015-09-01 15:50 ` Eli Zaretskii
2015-08-30 2:35 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83si711oyo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=guile-devel@gnu.org \
--cc=mark.kettenis@xs4all.nl \
--cc=xdje42@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox