From: Jonathan Larmour <jlarmour@redhat.com>
To: npyatkov@usa.net
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ICE, ecos and Insight
Date: Thu, 25 Jan 2001 09:31:00 -0000 [thread overview]
Message-ID: <3A7062DC.1DA5DDD2@redhat.com> (raw)
In-Reply-To: <20010125155313.17075.qmail@wwcst270.netaddress.usa.net>
npyatkov@usa.net wrote:
>
> Hi
> I wrote a server to support an HP ICE under Insight. Everything looks fine. I
> can download code into the target, walk through source code, read, modify and
> write memory and registers, view the stack. The only problem is Insight
> doesn'tshow any theads information.
> The same Insight binary set to 'remote serial' and talking to GDB stubs does
> it.
> Any ideas?
Yes. You have to provide some means for the ICE to retrieve the thread
status from eCos. Probably the best way is to add a vector to do this on
the eCos side, and when the ICE gets requested for thread information, it
will set the target to that vector and start running. The target can gather
the information using calls into GDB stub code and put it in a buffer which
the ICE can retrieve.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine
prev parent reply other threads:[~2001-01-25 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 7:53 npyatkov
2001-01-25 9:31 ` Jonathan Larmour [this message]
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=3A7062DC.1DA5DDD2@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=npyatkov@usa.net \
/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).