From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: janez.ulcakar@isystem.com, ulfh@ese.se,
ecos-maintainers@sources.redhat.com
Subject: Re: Debugger OS-awareness
Date: Fri, 28 Feb 2003 15:51:00 -0000 [thread overview]
Message-ID: <3E5F8569.90904@eCosCentric.com> (raw)
In-Reply-To: <20030228154403.GC15019@biferten.ma.tech.ascom.ch>
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
next prev parent reply other threads:[~2003-02-28 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 9:45 ulfh
2003-02-28 15:39 ` Jonathan Larmour
2003-02-28 15:44 ` Andrew Lunn
2003-02-28 15:51 ` Jonathan Larmour [this message]
2003-02-28 16:12 ` Janez Ulcakar
2003-02-28 16:20 ` Jonathan Larmour
2003-02-28 16:51 ` Janez Ulcakar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E5F8569.90904@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@sources.redhat.com \
--cc=janez.ulcakar@isystem.com \
--cc=ulfh@ese.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).