From: Doug Evans <xdje42@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: "Tom Tromey" <tromey@redhat.com>,
"Ludovic Courtès" <ludo@gnu.org>,
guile-user@gnu.org,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2 02/13] script language API for GDB: extension.[ch]
Date: Tue, 21 Jan 2014 20:35:54 -0800 [thread overview]
Message-ID: <CAP9bCMS4R8eEHWDX_hb8qKscLT=-=AExBLdQoHZTQz+VAinMSg@mail.gmail.com> (raw)
In-Reply-To: <87zjmomyt3.fsf@netris.org>
On Tue, Jan 21, 2014 at 8:21 PM, Mark H Weaver <mhw@netris.org> wrote:
> Tom Tromey <tromey@redhat.com> writes:
>
>>>>>>> "Ludovic" == Ludovic Courtès <ludo@gnu.org> writes:
>>
>> Ludovic> I guess this is another limitation of Guile’s current signal handling
>> Ludovic> strategy, and something we should fix.
>>
>> FWIW I think it would be sufficient for gdb if scm_system_async_mark, or
>> something like it, could be invoked from a signal handler. Then a
>> SIGINT in gdb could install an async callback that later checks gdb's
>> quit flag.
>
> As discussed on IRC, one way to accomplish this with current Guile is
> as follows: establish a dedicated thread whose sole job it is to call
> 'scm_system_async_mark_for_thread' as directed by messages received from
> a pipe. A signal handler can then schedule asyncs by writing messages
> to this pipe.
>
> We'll try to come up with an nicer solution at some point.
Righto, and thanks.
I'll implement this as a follow-on to the current patch series.
It'll be mostly just new code, and the current patch series is big enough.
prev parent reply other threads:[~2014-01-22 4:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52a7f3e8.e7ed440a.1c58.020f@mx.google.com>
[not found] ` <87vbyffcwu.fsf@fleche.redhat.com>
2013-12-24 18:05 ` [PATCH v2 02/13] script language API for GDB: extension.[ch] Doug Evans
2014-01-03 21:10 ` Ludovic Courtès
2014-01-06 21:53 ` Tom Tromey
2014-01-07 13:10 ` Ludovic Courtès
2014-01-07 16:02 ` Tom Tromey
2014-01-07 23:05 ` Ludovic Courtès
2014-01-08 3:17 ` Tom Tromey
2014-01-14 19:17 ` Tom Tromey
2014-01-15 14:52 ` Ludovic Courtès
2014-01-22 4:21 ` Mark H Weaver
2014-01-22 4:35 ` Doug Evans [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP9bCMS4R8eEHWDX_hb8qKscLT=-=AExBLdQoHZTQz+VAinMSg@mail.gmail.com' \
--to=xdje42@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.org \
--cc=mhw@netris.org \
--cc=tromey@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).