From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27436 invoked by alias); 8 Dec 2005 13:56:05 -0000 Received: (qmail 27420 invoked by uid 22791); 8 Dec 2005 13:56:04 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 08 Dec 2005 13:56:03 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EkMFd-0005QM-3t; Thu, 08 Dec 2005 08:56:01 -0500 Date: Thu, 08 Dec 2005 13:56:00 -0000 From: Daniel Jacobowitz To: Kim Lux Cc: gdb@sources.redhat.com Subject: Re: gdb for multicore processors ? Message-ID: <20051208135600.GA20771@nevyn.them.org> Mail-Followup-To: Kim Lux , gdb@sources.redhat.com References: <1134020836.27506.21.camel@localhost.localdomain> <1134020979.27506.23.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1134020979.27506.23.camel@localhost.localdomain> User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-12/txt/msg00087.txt.bz2 On Wed, Dec 07, 2005 at 10:49:39PM -0700, Kim Lux wrote: > One more thing. > > XGate code gets compiled to reside in flash. However, it gets relocated > to run from RAM as it runs much faster there. GDB will have to know > that the address it sees in RAM isn't the address it was compiled to. > The file format is elf, if that helps. How to handle this depends on how you do it. Traditionally you set the VMA in the ELF file to point to the RAM location; then everything will Just Work. > On Wed, 2005-12-07 at 22:47 -0700, Kim Lux wrote: > > Each processor has its own register set and instruction set. They are > > not the same. They share the same memory map, but the xgate processor > > addresses things differently. > > We are building the BDM, so theoretically we could connect 2 gdb > > processes to the same BDM, if that helps. That would allow us to have a > > separate GDB instance for each process. Or should one GDB instance > > handle both processors ? I strongly recommend using two GDB sessions, for now. It's a long-term design goal for GDB to be able to debug heterogenous systems, but no one has been working on it lately, and there's a long way to go. -- Daniel Jacobowitz CodeSourcery, LLC