Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Release the GIL while running a gdb command or expression
Date: Fri, 12 Oct 2018 16:56:00 -0000	[thread overview]
Message-ID: <6c7d1b6d-2d7a-dcaf-8d20-615bfb474af9@redhat.com> (raw)
In-Reply-To: <20181010202233.17985-1-tom@tromey.com>

On 10/10/2018 09:22 PM, Tom Tromey wrote:
> +
> +# Define a function for the thread

While at it, add missing periods?

> +def print_thread_hello():
> +   count = 0
> +   while count < 10:
> +      time.sleep(1)
> +      count += 1
> +      print ("Hello ( %d )" % count)
> +
> +# Create a thread and continue

Ditto.

> +try:
> +   thread.start_new_thread (print_thread_hello, ())
> +   gdb.execute ("continue", release_gil=True)
> +except:
> +   try:
> +      _thread.start_new_thread (print_thread_hello, ())
> +      gdb.execute ("continue", release_gil=True)

But what I came here for, is:

AFAICT, "release_gil" was not included in this version of
the patch, so that shouldn't be here either.  

The test should be failing because of that, I believe,
because GDB should be complaining that release_gil
is an invalid keyword.  Does the test somehow
happen to still pass with that?

> +   except:
> +      print ("Error: unable to start thread")

Thanks,
Pedro Alves


  parent reply	other threads:[~2018-10-12 16:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 20:23 Tom Tromey
2018-10-12 14:52 ` Phil Muldoon
2018-10-12 16:49 ` Pedro Alves
2018-10-12 16:51   ` Pedro Alves
2018-10-16 12:48   ` Tom Tromey
2018-10-16 14:50     ` Pedro Alves
2018-10-12 16:56 ` Pedro Alves [this message]
2018-10-16 13:05   ` Tom Tromey
2018-10-16 14:51     ` Pedro Alves
2018-10-16 21:39       ` Tom Tromey
2018-10-16 21:45         ` Tom Tromey
2018-10-24 18:08           ` Pedro Alves
2018-10-25 12:46             ` Phil Muldoon
2018-11-04 15:54             ` Tom Tromey
2019-01-29 13:02               ` Tom Tromey

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=6c7d1b6d-2d7a-dcaf-8d20-615bfb474af9@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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