From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21095 invoked by alias); 3 Oct 2011 16:16:33 -0000 Received: (qmail 21084 invoked by uid 22791); 3 Oct 2011 16:16:32 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Received: from qmta12.westchester.pa.mail.comcast.net (HELO qmta12.westchester.pa.mail.comcast.net) (76.96.59.227) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 03 Oct 2011 16:16:18 +0000 Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta12.westchester.pa.mail.comcast.net with comcast id gDly1h0051wpRvQ5CGGJQ0; Mon, 03 Oct 2011 16:16:18 +0000 Received: from [10.127.238.91] ([65.206.2.68]) by omta18.westchester.pa.mail.comcast.net with comcast id gGG51h01h1U2a2h3eGG7Tx; Mon, 03 Oct 2011 16:16:16 +0000 Subject: Re: Python: fetch value when building gdb.Value object [rediff] Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Paul Koning In-Reply-To: Date: Mon, 03 Oct 2011 16:16:00 -0000 Cc: Jan Kratochvil , gdb-patches@sourceware.org Content-Transfer-Encoding: quoted-printable Message-Id: <25071E96-2ACB-4ED0-83CE-BE3B7187BB31@comcast.net> References: <36B29E9D-F2B3-446F-AF8A-97254A3AAEE2@comcast.net> <20111001092852.GB11227@host1.jankratochvil.net> <20111001121642.GA29550@host1.jankratochvil.net> To: pmuldoon@redhat.com 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/msg00020.txt.bz2 On Oct 3, 2011, at 6:18 AM, Phil Muldoon wrote: > Jan Kratochvil writes: >=20 >> Updated for current HEAD: >>=20 >> On Sat, 01 Oct 2011 11:28:52 +0200, Jan Kratochvil wrote: >> On Wed, 28 Sep 2011 21:24:45 +0200, Phil Muldoon wrote: >>> What scenario will this test catch that the previous test won't? I'm >>> not saying you are incorrect, I just don't understand. What >>> error-trigger does the assignment to "inval" trigger? >>=20 >> I would prefer here a testcase more clearly showing the bug, attached be= low. >>=20 >> I believe the patch is right, as Phil hasn't yet agreed posting it only. >=20 > It looks great, thanks for doing this. Thanks all. Committed. paul