From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24327 invoked by alias); 22 Oct 2009 18:02:39 -0000 Received: (qmail 24273 invoked by uid 22791); 22 Oct 2009 18:02:38 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 22 Oct 2009 18:02:34 +0000 Received: from jupiter.vmware.com (mailhost5.vmware.com [10.16.68.131]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 73D9948019; Thu, 22 Oct 2009 11:02:33 -0700 (PDT) Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) by jupiter.vmware.com (Postfix) with ESMTP id 68127DC05F; Thu, 22 Oct 2009 11:02:33 -0700 (PDT) Message-ID: <4AE09CA9.2060401@vmware.com> Date: Thu, 22 Oct 2009 18:02:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: Doug Evans CC: "gdb-patches@sourceware.org" Subject: Re: Seems like a bug in target_read_stack / dcache_xfer_memory? References: <4ADB9759.7060305@vmware.com> <20091018225134.GA30546@caradoc.them.org> <4ADCA53C.2080703@vmware.com> <20091019183724.GA17923@caradoc.them.org> <4ADCBF6B.9050309@vmware.com> <20091019212817.GB3401@caradoc.them.org> <4ADCDBB7.2050500@vmware.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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: 2009-10/txt/msg00528.txt.bz2 Doug Evans wrote: > On Mon, Oct 19, 2009 at 2:35 PM, Michael Snyder wrote: >> Anyway, yes, that's what it does. dcache returns zero, >> and memory_xfer_partial bails out instead of trying the >> next target down the target stack. > > Hi. If it will help I'll play with your testcase tomorrow. > I'll also volunteer to make a pass through the code and add some comments. > [I mention that just in case you or someone is already in the process > of doing that.] Sure it will help. Thanks, Doug.