From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17522 invoked by alias); 19 Oct 2011 20:52:00 -0000 Received: (qmail 17513 invoked by uid 22791); 19 Oct 2011 20:51:59 -0000 X-SWARE-Spam-Status: No, hits=-7.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 19 Oct 2011 20:51:43 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9JKphBC020106 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 Oct 2011 16:51:43 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p9JKpg6L023067; Wed, 19 Oct 2011 16:51:42 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p9JKpf16017500; Wed, 19 Oct 2011 16:51:41 -0400 From: Tom Tromey To: Paul Koning Cc: gdb-patches@sourceware.org Subject: Re: Python: fetch value when building gdb.Value object References: <36B29E9D-F2B3-446F-AF8A-97254A3AAEE2@comcast.net> <21467A42-84A3-4DFD-83A9-28FFFB0A5C7F@comcast.net> <2F165381-183F-471F-8F55-457F08E6B008@comcast.net> Date: Wed, 19 Oct 2011 20:56:00 -0000 In-Reply-To: <2F165381-183F-471F-8F55-457F08E6B008@comcast.net> (Paul Koning's message of "Fri, 14 Oct 2011 16:29:54 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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 X-SW-Source: 2011-10/txt/msg00542.txt.bz2 >>>>> "Paul" == Paul Koning writes: Paul> At this point the change has been approved and committed (that Paul> happened before your comments arrived). So I guess we have a question Paul> of whether to change it back. Yes, I think so. I think the current approach is going to bite us later. We already have bugs open about bad memory management using gdb.Value. Tom