From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16110 invoked by alias); 21 Aug 2006 19:16:40 -0000 Received: (qmail 16095 invoked by uid 22791); 21 Aug 2006 19:16:40 -0000 X-Spam-Check-By: sourceware.org Received: from mx2.palmsource.com (HELO mx2.palmsource.com) (12.7.175.14) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 21 Aug 2006 19:16:37 +0000 Received: from localhost (localhost [127.0.0.1]) by localhost.domain.tld (Postfix) with ESMTP id AB9B525F14; Mon, 21 Aug 2006 12:16:35 -0700 (PDT) Received: from mx2.palmsource.com ([127.0.0.1]) by localhost (mx2.palmsource.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 02378-02; Mon, 21 Aug 2006 12:16:34 -0700 (PDT) Received: from ussunex01.palmsource.com (unknown [192.168.101.9]) by mx2.palmsource.com (Postfix) with ESMTP id 32D4925EE1; Mon, 21 Aug 2006 12:16:34 -0700 (PDT) Received: from 192.168.92.59 ([192.168.92.59]) by ussunex01.palmsource.com ([192.168.101.9]) via Exchange Front-End Server owa.palmsource.com ([10.0.20.17]) with Microsoft Exchange Server HTTP-DAV ; Mon, 21 Aug 2006 19:16:33 +0000 Received: from svmsnyderlnx by owa.palmsource.com; 21 Aug 2006 12:16:34 -0700 Subject: Re: Virtual Machine and GDB From: Michael Snyder To: Cai Qian Cc: Neo , gdb@sourceware.org In-Reply-To: References: <20060821000736.GA2596@nevyn.them.org> <44E9E787.9010202@cse.unl.edu> <44E9FBC3.4000201@cse.unl.edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 21 Aug 2006 19:16:00 -0000 Message-Id: <1156187793.9010.9.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 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: 2006-08/txt/msg00174.txt.bz2 On Mon, 2006-08-21 at 19:57 +0100, Cai Qian wrote: > OK. The VM does not have a debugger at the moment. That is why I try > to debug remotely. "New instruction set" means it is not i386, SPARC, > SuperH etc, and GDB does not support the arch yet. Right -- so once you get your gdbserver to talk to gdb, the next thing you have to do is teach gdb to understand your new architecture. If you look at some of the base architecture ports that you mentioned, for instance sh-tdep.c or h8300-tdep.c, these are examples of what I mean. They tell gdb how to interpret the register set etc. of the given target architecture. You need to write one of these for your target.