This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Problem about the uitron test
- To: ecos-discuss at sources dot redhat dot com
- Subject: Re: [ECOS] Problem about the uitron test
- From: Hugo 'NOx' Tyson <hmt at cygnus dot co dot ukx>
- Date: 25 Apr 2000 13:19:30 +0100
- Newsgroups: cygnus.sourceware.ecos.d
- Organization: Cygnus Solutions, a Red Hat company (Cambridge, UK)
- References: <Pine.LNX.4.10.10004211738420.689-100000@pyxue>
pyxue <root@t2-design.com> writes:
> Hi, I run several of the uItron tests provided by the ecos package, but I
> only get the result of " calling cyg_uitron_star". From the tests, I think
> that it is not right, it seems that the program doesn't run to the
> subroutine such as task1, task2.
Correct, that's not right. But without more info, we can't really comment
on what the cause might be.
What platform are you using? What is your configuration, or what have you
changed from the default configuration? Have you changed the uITRON
configuration points associated with task initialization?
> How can I solve the problem? Thank you!
Does the target stop when you hit CTRL-C in the GDB console? If so, you
should be able to find out what's going on. It helps to use built-in stubs
(for most platforms) so that you have thread-aware debugging - so you can
use "info threads" to inspect the thread states.
- Huge
--
The 20th Century brought unprecedented increases in worldwide numeracy and
literacy and incredible advances in technology, science and mathematics.
It was also the only century in the past or in any reasonable predictable
future apparently to contain only 99 years.