From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7601 invoked by alias); 14 Dec 2010 09:37:45 -0000 Received: (qmail 7593 invoked by uid 22791); 14 Dec 2010 09:37:45 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 14 Dec 2010 09:37:40 +0000 Received: (qmail 10103 invoked from network); 14 Dec 2010 09:37:38 -0000 Received: from unknown (HELO ?192.168.0.104?) (ams@127.0.0.2) by mail.codesourcery.com with ESMTPA; 14 Dec 2010 09:37:38 -0000 Message-ID: <4D073ADF.9020205@codesourcery.com> Date: Tue, 14 Dec 2010 09:37:00 -0000 From: Andrew Stubbs User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Pedro Alves CC: gdb-patches@sourceware.org, Mike Frysinger , toolchain-devel@blackfin.uclinux.org, Daniel Jacobowitz , Jie Zhang Subject: Re: [PATCH v2] gdbserver: bfin: new port References: <1291886957-12003-1-git-send-email-vapier@gentoo.org> <1291887065-12093-1-git-send-email-vapier@gentoo.org> <201012131843.59666.pedro@codesourcery.com> In-Reply-To: <201012131843.59666.pedro@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit 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: 2010-12/txt/msg00221.txt.bz2 On 13/12/10 18:43, Pedro Alves wrote: > Hmmm. These last 6 look to be some kind of pseudo registers, not > part of the ISA -- I'm quite surprised to see these here, as > part of the bfin core register set. I understand these to be > fdpic related; ISTR some discussion about making these be reported > with a new qXfer object? That'd be better, IMO. Right, the SH-2A FDPIC implementation uses qXfer to deal with the FDPIC settings. The SG++ gdb has a (more-or-less) target independent mechanism for retrieving the load maps. This has not been submitted upstream simply because it's not complete. The SH-2A FDPIC kernel does (did) not support breakpoints, and single stepping is (was) rather broken, so I never got further than being able to relocate the main program. For SH-2A, at least, the kernel does not expose the load maps as registers, but has extra ptrace queries PTRACE_GETFDPIC_EXEC and PTRACE_GETFDPIC_INTERP. The gdbserver reads these via qXfer:fdpic:read:exec and qXfer:fdpic:read:interp. Hope that helps Andrew