From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24150 invoked by alias); 8 Jul 2008 15:13:53 -0000 Received: (qmail 24136 invoked by uid 22791); 8 Jul 2008 15:13:52 -0000 X-Spam-Check-By: sourceware.org Received: from igw2.br.ibm.com (HELO igw2.br.ibm.com) (32.104.18.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 08 Jul 2008 15:13:30 +0000 Received: from mailhub3.br.ibm.com (mailhub3 [9.18.232.110]) by igw2.br.ibm.com (Postfix) with ESMTP id 571B217F4E8 for ; Tue, 8 Jul 2008 12:00:49 -0300 (BRT) Received: from d24av02.br.ibm.com (d24av02.br.ibm.com [9.18.232.47]) by mailhub3.br.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m68F5i2Q4087868 for ; Tue, 8 Jul 2008 12:05:46 -0300 Received: from d24av02.br.ibm.com (loopback [127.0.0.1]) by d24av02.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m68F5GKJ030865 for ; Tue, 8 Jul 2008 12:05:16 -0300 Received: from [9.8.8.213] ([9.8.8.213]) by d24av02.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m68F5FaY030799 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Jul 2008 12:05:16 -0300 Subject: Re: [PATCH] PPC - Stepping off breakpoints in non-stop mode From: Luis Machado Reply-To: luisgpm@linux.vnet.ibm.com To: Jonathan Larmour Cc: gdb-patches@sourceware.org In-Reply-To: <487380A9.2080300@eCosCentric.com> References: <4872C52C.1020701@eCosCentric.com> <1215489163.5333.29.camel@gargoyle> <487380A9.2080300@eCosCentric.com> Content-Type: text/plain Date: Tue, 08 Jul 2008 15:13:00 -0000 Message-Id: <1215529515.5333.32.camel@gargoyle> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 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: 2008-07/txt/msg00116.txt.bz2 On Tue, 2008-07-08 at 15:58 +0100, Jonathan Larmour wrote: > Luis Machado wrote: > > Hi Jonathan, > > > > Is this an embedded target? > > Yes, powerpc-eabi Ok. Changing "current_pc" from CORE_ADDR to ULONGEST fixes the problem. I'll check it in if folks don't have any objections about this. Thanks for letting me know. Luis