This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2] Improved ^c support for gdb/guile
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Doug Evans <xdje42 at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 17 Feb 2014 22:43:25 +0200
- Subject: Re: [PATCH v2] Improved ^c support for gdb/guile
- Authentication-results: sourceware.org; auth=none
- References: <wrbvbwejihe dot fsf at sspiff dot org> <wrbr471jxjg dot fsf at sspiff dot org>
- Reply-to: Eli Zaretskii <eliz at gnu dot 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?