From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13250 invoked by alias); 28 Feb 2003 15:44:17 -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 13242 invoked from network); 28 Feb 2003 15:44:17 -0000 Date: Fri, 28 Feb 2003 15:44:00 -0000 From: Andrew Lunn To: Jonathan Larmour Cc: janez.ulcakar@isystem.com, ulfh@ese.se, ecos-maintainers@sources.redhat.com Subject: Re: Debugger OS-awareness Message-ID: <20030228154403.GC15019@biferten.ma.tech.ascom.ch> References: <412607A31593D311B91E0000B45C283D1F43BB@ODEN01> <3E5F82B2.30205@eCosCentric.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E5F82B2.30205@eCosCentric.com> User-Agent: Mutt/1.4i X-Filter-Version: 1.6 (rubicon) X-SW-Source: 2003-02/txt/msg00070.txt.bz2 > >- 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. Andrew