From: ludo@gnu.org (Ludovic Courtès)
To: Eli Zaretskii <eliz@gnu.org>
Cc: xdje42@gmail.com, gdb-patches@sourceware.org, guile-devel@gnu.org
Subject: Re: [PATCH v2] Improved ^c support for gdb/guile
Date: Tue, 18 Feb 2014 23:08:00 -0000 [thread overview]
Message-ID: <87bny4589g.fsf@gnu.org> (raw)
In-Reply-To: <8338jg715m.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 18 Feb 2014 19:59:01 +0200")
Eli Zaretskii <eliz@gnu.org> skribis:
>> From: ludo@gnu.org (Ludovic Courtès)
>> Cc: xdje42@gmail.com, gdb-patches@sourceware.org, guile-devel@gnu.org
>> Date: Tue, 18 Feb 2014 18:45:53 +0100
>>
>> > Sorry, I meant why that code couldn't be used when Guile was built
>> > without pthreads.
>>
>> Because with the patch Doug posted, both the SIGINT thread and GDB’s
>> main thread would call libguile.
>>
>> A different strategy would need to be used when Guile lacks pthread
>> support.
>
> Could you perhaps suggest such a different strategy?
Something similar to Guile’s own strategy when compiled without pthread
support.
However, Doug is proposing on guile-devel an approach that may solve
that more elegantly.
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-02-18 23:08 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
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 [this message]
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=87bny4589g.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=guile-devel@gnu.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