From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17043 invoked by alias); 28 Feb 2003 15:51:08 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 17036 invoked from network); 28 Feb 2003 15:51:07 -0000 Message-ID: <3E5F8569.90904@eCosCentric.com> Date: Fri, 28 Feb 2003 15:51:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.2) Gecko/20021203 X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: Andrew Lunn Cc: janez.ulcakar@isystem.com, ulfh@ese.se, ecos-maintainers@sources.redhat.com Subject: Re: Debugger OS-awareness References: <412607A31593D311B91E0000B45C283D1F43BB@ODEN01> <3E5F82B2.30205@eCosCentric.com> <20030228154403.GC15019@biferten.ma.tech.ascom.ch> In-Reply-To: <20030228154403.GC15019@biferten.ma.tech.ascom.ch> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00071.txt.bz2 Andrew Lunn wrote: >>>- getting the specs on how to reach kernel object info from freeze mode >> >>freeze mode? We don't have much in the way of targets supporting power >>management at all (although the support exists) so I'm not clear what >>you're getting at. > > > This is running on an emulator. So i guess he means the emulator has > stopped executing instructions. He then wants to know how to poke > around the emulated memory to find out about tasks. > > He basically needs to implement in the emulator the functions Nick > added a few weeks ago to find out about current threads etc. True, but that can be problematic with a configurable operating system where the thread structure layout can change! There have been two approaches to this in the past. The first one, which has been preferred in the two examples (ICE support) so far that needed this support, was to save the target context in the ICE, set the PC to a special function pointed to from a well defined location, start the target going again and that function will gather the data required for the debugger, and then stop the target again when the function returns. The second approach, used by some simulators, is to have good enough support in the simulator and/or the port to run a ROM monitor, then communicate with it using the GDB remote protocol! This is probably slightly easier but has more overhead. Jifl -- eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts --[ "You can complain because roses have thorns, or you ]-- --[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine