From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16390 invoked by alias); 4 Sep 2009 20:18:52 -0000 Received: (qmail 16376 invoked by uid 22791); 4 Sep 2009 20:18:51 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_53,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 04 Sep 2009 20:18:44 +0000 Received: from spaceape7.eur.corp.google.com (spaceape7.eur.corp.google.com [172.28.16.141]) by smtp-out.google.com with ESMTP id n84KIeOA017798 for ; Fri, 4 Sep 2009 21:18:40 +0100 Received: from ywh15 (ywh15.prod.google.com [10.192.8.15]) by spaceape7.eur.corp.google.com with ESMTP id n84KIbcI020572 for ; Fri, 4 Sep 2009 13:18:38 -0700 Received: by ywh15 with SMTP id 15so1949198ywh.10 for ; Fri, 04 Sep 2009 13:18:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.235.5 with SMTP id i5mr17984206ybh.271.1252095517167; Fri, 04 Sep 2009 13:18:37 -0700 (PDT) In-Reply-To: <20090904201734.GY29075@codesourcery.com> References: <200909032303.56901.pedro@codesourcery.com> <20090903234357.GR29075@codesourcery.com> <20090904174903.GV29075@codesourcery.com> <20090904201734.GY29075@codesourcery.com> Date: Fri, 04 Sep 2009 20:18:00 -0000 Message-ID: Subject: Re: store.exp failure on i686-linux with newer gcc's From: Doug Evans To: Nathan Froyd Cc: Tom Tromey , Pedro Alves , gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00086.txt.bz2 On Fri, Sep 4, 2009 at 1:17 PM, Nathan Froyd wrot= e: > On Fri, Sep 04, 2009 at 12:38:23PM -0600, Tom Tromey wrote: >> I see now that read_pieced_value will only be called to fill in a lazy >> value. =A0So, you are correct, this can't happen for values on the >> history. >> >> This patch is ok. > > Thanks, committed. Thanks!