From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <xdje42@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Improved ^c support for gdb/guile
Date: Mon, 17 Feb 2014 20:43:00 -0000 [thread overview]
Message-ID: <834n3x8o7m.fsf@gnu.org> (raw)
In-Reply-To: <wrbr471jxjg.fsf@sspiff.org>
> From: Doug Evans <xdje42@gmail.com>
> Date: Mon, 17 Feb 2014 15:26:27 -0500
>
> Unworkable-as-is optimization trying to avoid queueing asyncs. Blech.
>
> I'm still seeing intermittent testsuite failures because Guile is
> getting an uncaught SIGINT.
Bother: is this the only way to fix these issues (whatever they are)?
Because you are quickly getting into non-Windows lands, so there's a
real risk that the Guile support will not be very useful on Windows
(except with Cygwin).
> +void
> +gdbscm_initialize_sigint (void)
> +{
> + siscm_sigint_pipe[0] = siscm_sigint_pipe[1] = -1;
> +
> + if (!SCM_USE_PTHREAD_THREADS)
> + {
> + warning (_("Guile does not have pthreads support."));
> + warning (_("Proper SIGINT handling for Guile will be unavailable."));
> + return;
> + }
The above is what worries me. Guile currently doesn't work in the
native MinGW build if configured with threads (it crashes, hangs,
etc.). Can't we have decent SIGINT handling without pthreads?
next prev parent reply other threads:[~2014-02-17 20:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 7:39 [PATCH] " Doug Evans
2014-02-17 9:27 ` Mark Kettenis
2014-02-17 16:06 ` Ludovic Courtès
2014-02-17 20:26 ` [PATCH v2] " Doug Evans
2014-02-17 20:43 ` Eli Zaretskii [this message]
2014-02-17 20:59 ` Doug Evans
2014-02-17 21:13 ` Eli Zaretskii
2014-02-18 0:37 ` Doug Evans
2014-02-18 11:20 ` Ludovic Courtès
2014-02-18 16:02 ` Eli Zaretskii
2014-02-18 16:45 ` Ludovic Courtès
2014-02-18 16:56 ` Eli Zaretskii
2014-02-18 17:46 ` Ludovic Courtès
2014-02-18 17:58 ` Eli Zaretskii
2014-02-18 23:08 ` Ludovic Courtès
2014-02-19 7:51 ` Mark H Weaver
2014-02-19 16:42 ` Eli Zaretskii
2014-02-18 17:31 ` Doug Evans
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=834n3x8o7m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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