This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Should GBD recognize ECOS Threads ?
- To: <ecos-discuss at sources dot redhat dot com>
- Subject: Re: [ECOS] Should GBD recognize ECOS Threads ?
- From: "RAY Electronic-Design GmbH" <info at raygmbh dot de>
- Date: Mon, 6 Aug 2001 11:42:32 +0100
- Cc: "Jonathan Larmour" <jlarmour at redhat dot com>
- References: <024001c11dd4$5a2cc400$fe78a8c0@raypc2> <3B6DED08.A6D87030@redhat.com>
- Reply-To: "RAY Electronic-Design GmbH" <info at raygmbh dot de>
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
>