From: Tom Tromey <tromey@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] [python] Fix Python 3 build and testsuite issues
Date: Tue, 20 Aug 2013 19:59:00 -0000 [thread overview]
Message-ID: <87d2p8gmlo.fsf@fleche.redhat.com> (raw)
In-Reply-To: <5213C6BA.7030703@redhat.com> (Phil Muldoon's message of "Tue, 20 Aug 2013 20:42:50 +0100")
>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:
Phil> @@ -236,7 +236,7 @@ class FrameVars(object):
Phil> # SYM may be a string instead of a symbol in the case of
Phil> # synthetic local arguments or locals. If that is the case,
Phil> # always fetch.
Phil> - if isinstance(sym, basestring):
Phil> + if isinstance(sym, str):
Phil> return True
Does this work in all versions?
I thought perhaps hasattr would be more robust here.
Phil> if (py_func != NULL)
Phil> {
Phil> - const char *function = NULL;
Phil> + char *function_to_free = NULL;
Phil> + const char *function;
Phil> if (gdbpy_is_string (py_func))
Phil> {
Phil> - function = PyString_AsString (py_func);
Phil> + function = function_to_free =
Phil> + python_string_to_host_string (py_func);
I think it's preferable to declare function_to_free in the innermost
scope.
Tom
next prev parent reply other threads:[~2013-08-20 19:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 14:50 Phil Muldoon
2013-08-19 16:19 ` Tom Tromey
2013-08-19 16:45 ` Phil Muldoon
2013-08-19 18:34 ` Tom Tromey
2013-08-20 19:43 ` Phil Muldoon
2013-08-20 19:59 ` Tom Tromey [this message]
2013-08-20 20:32 ` Phil Muldoon
2013-08-21 14:29 ` Phil Muldoon
2013-08-21 14:59 ` Tom Tromey
2013-08-21 15:37 ` Paul_Koning
2013-08-21 15:42 ` Tom Tromey
2013-08-21 14:56 ` Tom Tromey
2013-08-22 10:46 ` Phil Muldoon
2013-08-27 15:41 ` Tom Tromey
2013-08-29 10:08 ` 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=87d2p8gmlo.fsf@fleche.redhat.com \
--to=tromey@redhat.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