From: Mark H Weaver <mhw@netris.org>
To: Tom Tromey <tromey@redhat.com>
Cc: ludo@gnu.org (Ludovic Courtès),
guile-user@gnu.org, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 02/13] script language API for GDB: extension.[ch]
Date: Wed, 22 Jan 2014 04:26:00 -0000 [thread overview]
Message-ID: <87zjmomyt3.fsf@netris.org> (raw)
In-Reply-To: <87sisqv0dm.fsf@fleche.redhat.com> (Tom Tromey's message of "Tue, 14 Jan 2014 12:17:41 -0700")
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.
Mark
next prev parent reply other threads:[~2014-01-22 4:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 5:11 Doug Evans
2013-12-23 21:57 ` Tom Tromey
2013-12-24 18:05 ` Doug Evans
2014-01-03 21:11 ` Ludovic Courtès
2014-01-06 21:53 ` Tom Tromey
2014-01-07 13:10 ` Ludovic Courtès
2014-01-07 16:03 ` 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:26 ` Mark H Weaver [this message]
2014-01-22 4:36 ` 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=87zjmomyt3.fsf@netris.org \
--to=mhw@netris.org \
--cc=gdb-patches@sourceware.org \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.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