From: "Wiederhake, Tim" <tim.wiederhake@intel.com>
To: Eli Zaretskii <eliz@gnu.org>, Yao Qi <qiyaoltc@gmail.com>
Cc: "Jose E. Marchesi" <jose.marchesi@oracle.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: MemoryView missing from Python 2.4 and 2.6
Date: Tue, 07 Mar 2017 17:18:00 -0000 [thread overview]
Message-ID: <9676A094AF46E14E8265E7A3F4CCE9AF942A3B@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <8637epwf5j.fsf@gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1929 bytes --]
Hi all,
Let me recap:
The python bindings I wrote break GDB compilation for Python 2.6 and below.
I wrote a patch: https://sourceware.org/ml/gdb-patches/2017-02/msg00712.html
which I later revised to this: https://sourceware.org/ml/gdb-patches/2017-03/msg00039.html
The revised patch was OK'd to push by Yao: https://sourceware.org/ml/gdb-patches/2017-03/msg00058.html
under the premise that Jose or I confirm that it works with Python 2.6.
Jose confirmed the first version: https://sourceware.org/ml/gdb-patches/2017-02/msg00715.html
As the second version does not change the actual code, I guess that is fine, too.
Joel seems to be fine with the general solution as well: https://sourceware.org/ml/gdb-patches/2017-03/msg00072.html
Do I need Eli's OK for the added line in the documentation?
Otherwise, it'd like to go ahead and push this patch.
Regards,
Tim
> -----Original Message-----
> From: Yao Qi [mailto:qiyaoltc@gmail.com]
> Sent: Tuesday, March 7, 2017 11:33 AM
> To: Wiederhake, Tim <tim.wiederhake@intel.com>
> Cc: Jose E. Marchesi <jose.marchesi@oracle.com>; gdb-
> patches@sourceware.org
> Subject: Re: MemoryView missing from Python 2.4 and 2.6
>
> "Wiederhake, Tim" <tim.wiederhake@intel.com> writes:
>
> > Thanks for the pointer. I've attached a revised version of the patch.
>
> Hi Tim,
> Did you run py-record-btrace.xp with python 2.6? or probably Jose can help
> to run it with python 2.6.
>
> If the test Tim added pass with both python 2.6 and python 3, your patch is
> OK.
>
> --
> Yao (é½å°§)
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
\x16º&Öéj×!zÊÞ¶êç×~øßib²Ö«r\x18\x1dnr\x17¬
next prev parent reply other threads:[~2017-03-07 17:18 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
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 [this message]
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=9676A094AF46E14E8265E7A3F4CCE9AF942A3B@irsmsx105.ger.corp.intel.com \
--to=tim.wiederhake@intel.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.com \
--cc=qiyaoltc@gmail.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