From: "RAY Electronic-Design GmbH" <info@raygmbh.de>
To: <ecos-discuss@sources.redhat.com>
Cc: "Jonathan Larmour" <jlarmour@redhat.com>
Subject: Re: [ECOS] Should GBD recognize ECOS Threads ?
Date: Mon, 06 Aug 2001 04:00:00 -0000 [thread overview]
Message-ID: <025701c11e65$30a51560$fe78a8c0@raypc2> (raw)
In-Reply-To: <3B6DED08.A6D87030@redhat.com>
My Redboot ROM monitor is a build from last weeks cvs.
Platform is Triscend A7 eval Board, i adapted a 1.3.1 Board-Package from
Triscend to the actual ecos CVS.
Raymund Hofmann
----- Original Message -----
From: "Jonathan Larmour" <jlarmour@redhat.com>
To: "Raymund Hofmann" <rhofmann@raygmbh.de>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Monday, August 06, 2001 2:04 AM
Subject: Re: [ECOS] Should GBD recognize ECOS Threads ?
> Raymund Hofmann wrote:
> >
> > Should GDB be aware of the threads in ECOS ?
> > In my experiments so far, for example running the example :
"twothreads",
> > GDB seems not to list the created threads.
> > In the configuration by default "CYGACC_CALL_IF_DBG_SYSCALL_SET" is
checked,
> > but the entry
> > CYGNUM_CALL_IF_DBG_SYSCALL in the virtual vector table points to :
> > "nop_service" int the rom Monitor, before and after downloading and
starting
> > a ram application.
> > Am i guessing right that this is currently not implemented ?
>
> Yes GDB should be aware of eCos threads, but without basic information we
> can't help you work out why not. What is your ROM monitor (if not RedBoot,
> what age is it as well)? And what is your platform?
>
> Jifl
> --
> Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
> Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
>
next prev parent reply other threads:[~2001-08-06 4:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-05 9:30 Raymund Hofmann
2001-08-05 18:03 ` Jonathan Larmour
2001-08-06 4:00 ` RAY Electronic-Design GmbH [this message]
2001-08-06 9:22 ` Jonathan Larmour
2001-08-07 4:14 ` RAY Electronic-Design GmbH
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='025701c11e65$30a51560$fe78a8c0@raypc2' \
--to=info@raygmbh.de \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@redhat.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).