From mboxrd@z Thu Jan  1 00:00:00 1970
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
Message-id: <3A7062DC.1DA5DDD2@redhat.com>
References: <20010125155313.17075.qmail@wwcst270.netaddress.usa.net>
X-SW-Source: 2001-01/msg00427.html

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