From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31078 invoked by alias); 28 Feb 2003 16:12:02 -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 31031 invoked from network); 28 Feb 2003 16:12:01 -0000 From: "Janez Ulcakar" To: "Jonathan Larmour" , "Andrew Lunn" Cc: Subject: RE: Debugger OS-awareness Date: Fri, 28 Feb 2003 16:12:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <3E5F8569.90904@eCosCentric.com> X-OriginalArrivalTime: 28 Feb 2003 16:11:03.0610 (UTC) FILETIME=[FDF219A0:01C2DF43] X-SW-Source: 2003-02/txt/msg00072.txt.bz2 Hi, You're correct in your assumptions. We've encountered that 'special function spawned by the ICE' approach before, and I think it's better suited for an ICE. a) Does eCos already provide such a function (how's it called, where does it take it's params from, and where do we read the results from and what format) or b) should a debugger (we) provide a C source that the user includes in his build regards janez -----Original Message----- From: Jonathan Larmour [mailto:jifl@eCosCentric.com] Sent: Friday, February 28, 2003 16:51 To: Andrew Lunn Cc: janez.ulcakar@isystem.com; ulfh@ese.se; ecos-maintainers@sources.redhat.com Subject: Re: Debugger OS-awareness 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