This is the mail archive of the
ecos-maintainers@sources.redhat.com
mailing list for the eCos project.
RE: Debugger OS-awareness
- From: "Janez Ulcakar" <janezu at asystelectronic dot si>
- To: "Jonathan Larmour" <jifl at eCosCentric dot com>
- Cc: "Andrew Lunn" <andrew dot lunn at ascom dot ch>,<ecos-maintainers at sources dot redhat dot com>
- Date: Fri, 28 Feb 2003 17:50:18 +0100
- Subject: RE: Debugger OS-awareness
Thanks so far. I think we'll be able to delve in next month.
-----Original Message-----
From: Jonathan Larmour [mailto:jifl at eCosCentric dot com]
Sent: Friday, February 28, 2003 17:20
To: Janez Ulcakar
Cc: Andrew Lunn; ecos-maintainers at sources dot redhat dot com
Subject: Re: Debugger OS-awareness
Janez Ulcakar wrote:
> 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)
It wasn't made generic but there's one that was *intended* to be made
generic in the hal/v85x ports. Search for CYGDBG_HAL_V850_ICE, and in
particular look at hal/v85x/v850/current/src/v850_ice.cxx.
There's also one for the ARM at hal/arm/arch/current/src/arm_stub.c but
that isn't quite as good as it requires stubs to be included in
applications.
> b) should a debugger (we) provide a C source that the user includes in his
> build
Ideally such support should be built into the eCos port! If it's for an
existing target, contributing it back to the community would be the best
thing for users. Of course the support would want to be default off for
users who don't need it.
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