From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10708 invoked by alias); 17 Mar 2010 19:00:41 -0000 Received: (qmail 10699 invoked by uid 22791); 17 Mar 2010 19:00:41 -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-2.vmware.com (HELO smtp-outbound-2.vmware.com) (65.115.85.73) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 17 Mar 2010 19:00:37 +0000 Received: from jupiter.vmware.com (mailhost5.vmware.com [10.16.68.131]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 8B99B4E042 for ; Wed, 17 Mar 2010 12:00:36 -0700 (PDT) Received: from [10.20.125.19] (unknown [10.20.125.19]) by jupiter.vmware.com (Postfix) with ESMTP id 7F538DC1D6; Wed, 17 Mar 2010 12:00:36 -0700 (PDT) Message-ID: <4BA126D4.5000109@vmware.com> Date: Wed, 17 Mar 2010 19:00:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.22 (X11/20090609) MIME-Version: 1.0 To: Michael Snyder , "gdb@sourceware.org" Subject: Re: Understanding aspaces References: <4BA122FE.7030604@vmware.com> <20100317185038.GA10403@caradoc.them.org> In-Reply-To: <20100317185038.GA10403@caradoc.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2010-03/txt/msg00107.txt.bz2 Daniel Jacobowitz wrote: > On Wed, Mar 17, 2010 at 11:44:14AM -0700, Michael Snyder wrote: >> Or to be more accurate, "I'm not understanding aspaces". >> A little help would be appreciated. >> >> The basic problem at the moment: software_breakpoint_inserted_here_p is >> failing to recognize the breakpoint address, because the aspace of the >> breakpoint does not match the aspace of the regcache. >> >> This is remote debugging between native linux-x86_64 and gdbserver. > > Is this HEAD? I just recently fixed a similar bug. > >> The register aspace, however, comes from the current ptid, and >> has num equal to some large value that varies from one run to the >> next. I'm not sure how it's derived. > > Sounds like the same bug. Must be. I'm a few weeks back from HEAD. Thanks.