public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org,  guile-user@gnu.org
Subject: Re: [PATCH v2 02/13] script language API for GDB: extension.[ch]
Date: Tue, 07 Jan 2014 23:05:00 -0000	[thread overview]
Message-ID: <87vbxv8kag.fsf@gnu.org> (raw)
In-Reply-To: <87iotvixu4.fsf@fleche.redhat.com> (Tom Tromey's message of "Tue,	07 Jan 2014 09:02:59 -0700")

Tom Tromey <tromey@redhat.com> skribis:

> Ludovic> Would it work, upon SIGINT, to do something like:
> Ludovic>   (system-async-mark (lambda ()
> Ludovic>                        (throw 'system-error ... EINTR)))
> Ludovic> That would eventually raise an exception in Scheme code.
>
> According to the Guile docs one must use scm_sigaction, since
> scm_system_async_mark is not async-signal-safe.

Oh, right.  This could be worked around by having a separate signal
delivery thread (which is what Guile currently does internally), but
that’s not so great.

I guess this is another limitation of Guile’s current signal handling
strategy, and something we should fix.

Ludo’.

  reply	other threads:[~2014-01-07 23:05 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 [this message]
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
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=87vbxv8kag.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=guile-user@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).