From: Tom Tromey <tromey@redhat.com>
To: <Paul_Koning@Dell.com>
Cc: <pmuldoon@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [python] [patch] PR 13369/13374
Date: Mon, 21 Nov 2011 19:59:00 -0000 [thread overview]
Message-ID: <m3aa7p9rh9.fsf@fleche.redhat.com> (raw)
In-Reply-To: <09787EF419216C41A903FD14EE5506DD030EBD9671@AUSX7MCPC103.AMER.DELL.COM> (Paul Koning's message of "Mon, 21 Nov 2011 05:50:06 -0600")
>>>>> "Paul" == <Paul_Koning@Dell.com> writes:
>> + /* Note -- this is not thread-safe. */
Paul> Does the comment "not thread safe" indicate that this is a spot where
Paul> the GIL should be acquired and isn't currently? Or doesn't the GIL
Paul> help for that?
The comment refers to the code being called here.
I think the comment can be removed. It isn't ok to call gdb stuff from
other Python threads anyway.
Tom
next prev parent reply other threads:[~2011-11-21 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 11:42 Phil Muldoon
2011-11-21 11:50 ` Paul_Koning
2011-11-21 19:59 ` Tom Tromey [this message]
2011-11-21 20:09 ` Tom Tromey
2011-11-22 12:16 ` Phil Muldoon
2011-11-22 18:01 ` Tom Tromey
2011-11-28 16:02 ` Phil Muldoon
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=m3aa7p9rh9.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=Paul_Koning@Dell.com \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@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