From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MM5S9-0004ER-UC for qemu-devel@nongnu.org; Wed, 01 Jul 2009 15:26:45 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MM5S4-0004ED-Eh for qemu-devel@nongnu.org; Wed, 01 Jul 2009 15:26:44 -0400 Received: from [199.232.76.173] (port=43208 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MM5S4-0004EA-6v for qemu-devel@nongnu.org; Wed, 01 Jul 2009 15:26:40 -0400 Received: from mx20.gnu.org ([199.232.41.8]:22459) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MM5S3-0002gG-VW for qemu-devel@nongnu.org; Wed, 01 Jul 2009 15:26:40 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MM5S2-0007XB-Ox for qemu-devel@nongnu.org; Wed, 01 Jul 2009 15:26:39 -0400 Date: Wed, 1 Jul 2009 12:26:37 -0700 From: Nathan Froyd Subject: Re: [Qemu-devel] Extending gdb stub implementation with ARM926 registers support Message-ID: <20090701192637.GF1119@codesourcery.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Wed, Jul 01, 2009 at 09:05:35PM +0400, Dmitry Smirnov wrote: > As you know, ARM926 has few registers that are not supported by > current gdb stub. For instance, SPSRs, R13_abt, etc. > > Is it possible to extend gdb stub in this way? > I would try to do it by myself, but I need some guidelines. Obviously, > I need to extend the stub with some xml files describing these > registers and add its processing somehow. How? You'll need to: - Write the necessary XML file(s) in gdb-xml/. I believe the format of the XML files is minimally documented in the GDB manual. Reading other XML files can help as well (both in QEMU and GDB itself); - Add those XML file(s) to gdb_xml_files in configure for appropriate targets; - Add appropriate calls to gdb_register_coprocessor in target-arm/helper.c:cpu_arm_init. -Nathan