From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 73917 invoked by alias); 29 Nov 2017 10:39:49 -0000 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 Received: (qmail 73898 invoked by uid 89); 29 Nov 2017 10:39:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=3.4 required=5.0 tests=AWL,BAYES_00,FOREIGN_BODY,KB_WAM_FROM_NAME_SINGLEWORD,RCVD_IN_DNSWL_NONE,SPF_PASS,T_FILL_THIS_FORM_SHORT autolearn=no version=3.3.2 spammy=XML, H*r:sk:gdb@sou, EMail, E-Mail X-HELO: dedi548.your-server.de Received: from dedi548.your-server.de (HELO dedi548.your-server.de) (85.10.215.148) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 29 Nov 2017 10:39:47 +0000 Received: from [88.198.220.130] (helo=sslproxy01.your-server.de) by dedi548.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.85_2) (envelope-from ) id 1eJzmL-0002R7-8z for gdb@sourceware.org; Wed, 29 Nov 2017 11:39:45 +0100 Received: from [82.135.62.35] (helo=mail.embedded-brains.de) by sslproxy01.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eJzmK-0002dy-VP for gdb@sourceware.org; Wed, 29 Nov 2017 11:39:45 +0100 Received: from localhost (localhost.localhost [127.0.0.1]) by mail.embedded-brains.de (Postfix) with ESMTP id 6D9702A109A for ; Wed, 29 Nov 2017 11:39:38 +0100 (CET) Received: from mail.embedded-brains.de ([127.0.0.1]) by localhost (zimbra.eb.localhost [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id Ah-p1vVwcxE4 for ; Wed, 29 Nov 2017 11:39:36 +0100 (CET) Received: from localhost (localhost.localhost [127.0.0.1]) by mail.embedded-brains.de (Postfix) with ESMTP id 587C52A166C for ; Wed, 29 Nov 2017 11:39:36 +0100 (CET) Received: from mail.embedded-brains.de ([127.0.0.1]) by localhost (zimbra.eb.localhost [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ifTUEVCSjcZ5 for ; Wed, 29 Nov 2017 11:39:36 +0100 (CET) Received: from [192.168.96.129] (unknown [192.168.96.129]) by mail.embedded-brains.de (Postfix) with ESMTPSA id 407F12A109A for ; Wed, 29 Nov 2017 11:39:36 +0100 (CET) To: gdb@sourceware.org From: Sebastian Huber Subject: How can I figure out the register numbers for a remote target stub? Message-ID: Date: Wed, 29 Nov 2017 10:39:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2017-11/txt/msg00032.txt.bz2 Hello, I would like to extend the RTEMS GDB remote target stub to support=20 PowerPC (e500, e6500).=C2=A0 In the ARM support we have some magic register= =20 numbers: https://git.rtems.org/rtems/tree/cpukit/libdebugger/rtems-debugger-arm.c#n1= 32 |/* * Debugger registers layout. */ #define REG_R0 0 #define REG_R1 1=20 #define REG_R2 2 #define REG_R3 3 #define REG_R4 4 #define REG_R5 5=20 #define REG_R6 6 #define REG_R7 7 #define REG_R8 8 #define REG_R9 9=20 #define REG_R10 10 #define REG_R11 11 #define REG_R12 12 #define REG_SP=20 13 #define REG_LR 14 #define REG_PC 15 #define REG_CPSR 25 How can I=20 find the corresponding numbers for the PowerPC? There is a comment in=20 (gdb/ppc-tdep.h): /* Register number constants. These are GDB internal=20 register numbers; they are not used for the simulator or remote targets.=20 Extra SPRs (those other than MQ, CTR, LR, XER, SPEFSCR) are given=20 numbers above PPC_NUM_REGS. So are segment registers and other=20 target-defined registers. */ enum { PPC_R0_REGNUM =3D 0, PPC_F0_REGNUM =3D= =20 32, I cannot find the numbers which are used for remote targets. Are=20 they defined by the XML files in gdb/features/rs6000? | --=20 Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.huber@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine gesch=C3=A4ftliche Mitteilung im Sinne des EHUG.