public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: "Janez Ulcakar" <janezu@asystelectronic.si>
To: "Jonathan Larmour" <jifl@eCosCentric.com>
Cc: "Andrew Lunn" <andrew.lunn@ascom.ch>,
	<ecos-maintainers@sources.redhat.com>
Subject: RE: Debugger OS-awareness
Date: Fri, 28 Feb 2003 16:51:00 -0000	[thread overview]
Message-ID: <OIEOKFLCBNDKFNELKGEHCELPDAAA.janezu@asystelectronic.si> (raw)
In-Reply-To: <3E5F8C38.204@eCosCentric.com>

Thanks so far. I think we'll be able to delve in next month.

-----Original Message-----
From: Jonathan Larmour [mailto:jifl@eCosCentric.com]
Sent: Friday, February 28, 2003 17:20
To: Janez Ulcakar
Cc: Andrew Lunn; ecos-maintainers@sources.redhat.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


      reply	other threads:[~2003-02-28 16: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
2003-02-28 16:12       ` Janez Ulcakar
2003-02-28 16:20         ` Jonathan Larmour
2003-02-28 16:51           ` Janez Ulcakar [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=OIEOKFLCBNDKFNELKGEHCELPDAAA.janezu@asystelectronic.si \
    --to=janezu@asystelectronic.si \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=jifl@eCosCentric.com \
    /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).