From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1712 invoked by alias); 24 Feb 2017 16:06:13 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 1700 invoked by uid 89); 24 Feb 2017 16:06:12 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=H*f:sk:9676A09, H*i:sk:9676A09 X-HELO: mail-wm0-f46.google.com Received: from mail-wm0-f46.google.com (HELO mail-wm0-f46.google.com) (74.125.82.46) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 24 Feb 2017 16:06:11 +0000 Received: by mail-wm0-f46.google.com with SMTP id 196so9425612wmm.1 for ; Fri, 24 Feb 2017 08:06:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=DdFuH17m/r7yYOfzQU7N4LheZt11ItLJfMZ1IdZ+4mY=; b=NFobQIeGFOUTzFQEBxZNLcU2GFEqxCQRh4Xe5ZYmGGHRvZZaYIYwHYPtGhb40VBcGw SsTCWW4yd8PofYl8mgtav0hXiMWCE8z9nhGAKXNvzqrtmnitIHHYZjzpdKSde4LW/Yar mfrABzKAH4iq2OOhhfU3cUippsqhB3tK8CLaAi+zTeyW3RMJQdjQmWLoAMsX6GZOgfIM R6+nieffBN78QdUHljt+Ku5zYHLzjpJch62okuZwzbSVCjjltD9tu8jPKSiEEId2k67T ALyaxNApAg3pxJ0wLB4IDKVR43Uyp0YjusPJgtz8LMq9zDSMofHd7xzlT+umL9NIBpeE 9niA== X-Gm-Message-State: AMke39mf/oyk4mEWmL2dblh4CzEe2ENPZx6cbt3wHKvWRohHZbbxMQJyVYtqMhlLJck9gQ== X-Received: by 10.28.215.200 with SMTP id o191mr3387012wmg.118.1487952369334; Fri, 24 Feb 2017 08:06:09 -0800 (PST) Received: from E107787-LIN ([194.214.185.158]) by smtp.gmail.com with ESMTPSA id e74sm2886019wmd.2.2017.02.24.08.06.08 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Fri, 24 Feb 2017 08:06:08 -0800 (PST) From: Yao Qi To: "Wiederhake\, Tim" Cc: "Jose E. Marchesi" , "gdb-patches\@sourceware.org" Subject: Re: MemoryView missing from Python 2.4 and 2.6 References: <87o9xsx38r.fsf@oracle.com> <20170223225946.snir4ab6twc7vo7n@localhost> <9676A094AF46E14E8265E7A3F4CCE9AF9417D1@irsmsx105.ger.corp.intel.com> Date: Fri, 24 Feb 2017 16:06:00 -0000 In-Reply-To: <9676A094AF46E14E8265E7A3F4CCE9AF9417D1@irsmsx105.ger.corp.intel.com> (Tim Wiederhake's message of "Fri, 24 Feb 2017 10:37:46 +0000") Message-ID: <86h93j7evn.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2017-02/txt/msg00682.txt.bz2 "Wiederhake, Tim" writes: Hi Tim, > 2) Refactor "gdb.Membuf" from python/py-inferior.c into its own file and = use > that. I don't like this idea too much because it is basically reinventing= the > wheel and gdb.Membuf is less versatile than build-in buffers, strings, et= c. > > 3) Use the "new style buffer API" and limit GDB's support to Python >=3D = 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. > > 4) Return a string in "gdb.BtraceInstruction.data ()". The instruction da= ta can > potentially contain null bytes which can cause issues for obvious reasons. Before we think of them carefully, could you tell us how is the python api "gdb.BtraceInstruction.data ()" affected by these options? From a GDB python api user's point of view, they use gdb.BtraceInstruction.data() in their python code, if we take one of these options, and change it, do they need to change their code too? Once "gdb.BtraceInstruction.data()" is released, it is harder to change it in the later releases. Secondly, GDB can't be built with python 2.6 and 2.4, we still need to think about whether python 2.4 and 2.6 is supported or not in GDB 8.0 release. --=20 Yao (=E9=BD=90=E5=B0=A7)