Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <xdje42@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 02/13] script language API for GDB: extension.[ch]
Date: Mon, 23 Dec 2013 21:57:00 -0000	[thread overview]
Message-ID: <87vbyffcwu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <52a7f3e8.e7ed440a.1c58.020f@mx.google.com> (Doug Evans's message	of "Tue, 10 Dec 2013 21:10:37 -0800")

>>>>> "Doug" == Doug Evans <xdje42@gmail.com> writes:

Doug> +void
Doug> +clear_quit_flag (void)
Doug> +{
Doug> +  int i;
Doug> +  const struct extension_language_defn *extlang;
Doug> +
Doug> +  ALL_ENABLED_EXTENSION_LANGUAGES (i, extlang)
Doug> +    {
Doug> +      if (extlang->ops->clear_quit_flag != NULL)
Doug> +	extlang->ops->clear_quit_flag (extlang);
Doug> +    }
Doug> +
Doug> +  quit_flag = 0;
Doug> +}

I don't think this will work properly.  It seems to me that a given
interrupt may be processed multiple times -- once by each extension
language.

The way it works right now, if Python handles the "quit", then Python
clears the flag -- which also clears gdb's notion of the flag, because
the two are identical.

With the above it seems that Python could clear its flag -- but leave
other extension languages unaware that the interrupt was handled.  So, a
subsequent call into Guile will presumably erroneously throw an
exception.

Tom


  reply	other threads:[~2013-12-23 21:57 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 [this message]
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
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=87vbyffcwu.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.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