From: <Paul.Koning@dell.com>
To: <tim.wiederhake@intel.com>
Cc: <jose.marchesi@oracle.com>, <gdb-patches@sourceware.org>
Subject: Re: MemoryView missing from Python 2.4 and 2.6
Date: Fri, 24 Feb 2017 16:14:00 -0000 [thread overview]
Message-ID: <BA1B1EEF-3515-45D7-BCF2-6A7D2380D2E5@dell.com> (raw)
In-Reply-To: <86h93j7evn.fsf@gmail.com>
"Wiederhake, Tim" <tim.wiederhake@intel.com> writes:
> ...
> 3) Use the "new style buffer API" and limit GDB's support to Python >= 2.6.
> In this case we would have to limit the supported Python versions anyway so
> on the one hand there is not much reason to not throw out 2.6 as well. On the
> other hand, there still seem to be some Python 2.6 users.
That makes sense.
> 4) Return a string in "gdb.BtraceInstruction.data ()". The instruction data can
> potentially contain null bytes which can cause issues for obvious reasons.
Python has no problem at all with null bytes in strings.
paul
next prev parent reply other threads:[~2017-02-24 16:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 16:48 Jose E. Marchesi
2017-02-23 17:06 ` Jose E. Marchesi
2017-02-23 22:59 ` Yao Qi
2017-02-24 10:37 ` Wiederhake, Tim
2017-02-24 16:06 ` Yao Qi
2017-02-24 16:14 ` Paul.Koning [this message]
2017-02-28 10:53 ` Wiederhake, Tim
2017-02-28 12:51 ` Jose E. Marchesi
2017-03-07 0:21 ` Joel Brobecker
2017-03-07 13:38 ` Wiederhake, Tim
2017-03-07 15:27 ` Joel Brobecker
2017-03-03 10:21 ` Yao Qi
2017-03-06 8:56 ` Wiederhake, Tim
2017-03-07 10:32 ` Yao Qi
2017-03-07 17:18 ` Wiederhake, Tim
2017-03-17 15:59 ` Yao Qi
2017-03-17 16:39 ` Jose E. Marchesi
2017-03-20 9:04 ` Yao Qi
2017-03-20 22:44 ` Yao Qi
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=BA1B1EEF-3515-45D7-BCF2-6A7D2380D2E5@dell.com \
--to=paul.koning@dell.com \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.com \
--cc=tim.wiederhake@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