From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15474 invoked by alias); 22 Jan 2013 13:43:38 -0000 Received: (qmail 15457 invoked by uid 22791); 22 Jan 2013 13:43:36 -0000 X-SWARE-Spam-Status: No, hits=-5.1 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from ch1ehsobe003.messaging.microsoft.com (HELO ch1outboundpool.messaging.microsoft.com) (216.32.181.183) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 Jan 2013 13:43:08 +0000 Received: from mail35-ch1-R.bigfish.com (10.43.68.233) by CH1EHSOBE002.bigfish.com (10.43.70.52) with Microsoft SMTP Server id 14.1.225.23; Tue, 22 Jan 2013 13:43:06 +0000 Received: from mail35-ch1 (localhost [127.0.0.1]) by mail35-ch1-R.bigfish.com (Postfix) with ESMTP id 8B3CDE071F; Tue, 22 Jan 2013 13:43:06 +0000 (UTC) X-Forefront-Antispam-Report: CIP:59.163.77.45;KIP:(null);UIP:(null);IPV:NLI;H:KCHJEXHC01.kpit.com;RD:59.163.77.45.static.vsnl.net.in;EFVD:NLI X-SpamScore: -5 X-BigFish: VPS-5(zzbafdMzz1ee6h1de0h1202h1e76h1d1ah1d2ahzzz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h14ddh1504h1537h153bh15d0h162dh1631h1758h18e1h1155h) Received: from mail35-ch1 (localhost.localdomain [127.0.0.1]) by mail35-ch1 (MessageSwitch) id 1358862185854470_26981; Tue, 22 Jan 2013 13:43:05 +0000 (UTC) Received: from CH1EHSMHS009.bigfish.com (snatpool3.int.messaging.microsoft.com [10.43.68.228]) by mail35-ch1.bigfish.com (Postfix) with ESMTP id CDFBA1603F9; Tue, 22 Jan 2013 13:43:05 +0000 (UTC) Received: from KCHJEXHC01.kpit.com (59.163.77.45) by CH1EHSMHS009.bigfish.com (10.43.70.9) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 22 Jan 2013 13:43:04 +0000 Received: from KCHJEXMB02.kpit.com ([169.254.2.51]) by KCHJEXHC01.kpit.com ([172.10.15.73]) with mapi id 14.02.0247.003; Tue, 22 Jan 2013 19:12:54 +0530 From: Kaushik Phatak To: Pedro Alves CC: "gdb-patches@sourceware.org" Subject: RE: [RFA 4/5] New port: CR16: gdbserver Date: Tue, 22 Jan 2013 13:43:00 -0000 Message-ID: References: <50CB742E.9090506@redhat.com> <50F97ABF.4060203@redhat.com> In-Reply-To: <50F97ABF.4060203@redhat.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: kpitcummins.com 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: 2013-01/txt/msg00525.txt.bz2 Hi Pedro, Thanks for your feedback. > No, this needs to be fixed. The .dat registers must agree with GDB's rem= ote > register set. Once that is fixed, you'll be able to put more registers > in the "expedite" set I am working on these points. From what I see, my cr16_regmap needs to be 4-byte aligned so that ptrace calls within linux-low.c can use these without causing any I/O errors. The updated reg.dat file would not match in offset to cr16_regmap, but would match gdb. Some additional code would be needed to handle the padding and packing thro= ugh=20 ptrace in the kernel. This would allow the correct register number to be=20 accessed which would match gdb as well as reg-cr16.dat. Let me know if you have any thoughts on this. Regards, Kaushik