Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>,
	       "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] python: accept address and explicit locations in gdb.decode_line
Date: Thu, 23 Jun 2016 15:27:00 -0000	[thread overview]
Message-ID: <576BFFFB.1050304@redhat.com> (raw)
In-Reply-To: <A78C989F6D9628469189715575E55B23332EFA94@IRSMSX104.ger.corp.intel.com>

On 06/23/2016 02:15 AM, Metzger, Markus T wrote:

> /* Architecture and language to be used in callbacks from
>    the Python interpreter.  */
> struct gdbarch *python_gdbarch;
> const struct language_defn *python_language;
> 
> 
> The function this patch is modifying is:
> 
> /* A Python function which is a wrapper for decode_line_1.  */
> 
> static PyObject *
> gdbpy_decode_line (PyObject *self, PyObject *args)
> 
> 
> I'd say this qualifies as a callback from the Python interpreter.

I see what's happening. The code is littered with calls to
ensure_python_env (..., current_language), which saves current_language
into a structure. This gets saved and restored every time the
interpreter is entered/left. "python_language" is really the
"current_language_used_by_python." :-)

So I'd say I was incorrect and your original patch is correct. Good job
keeping me "honest!"

Keith


  reply	other threads:[~2016-06-23 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 14:33 Markus Metzger
2016-06-22 20:14 ` Keith Seitz
2016-06-23  9:15   ` Metzger, Markus T
2016-06-23 15:27     ` Keith Seitz [this message]
2016-06-29 14:15       ` Metzger, Markus T
2016-10-06 17:42         ` Pedro Alves

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=576BFFFB.1050304@redhat.com \
    --to=keiths@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.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