public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Hugo 'NOx' Tyson <hmt@cygnus.co.ukx>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Problem about the uitron test
Date: Tue, 25 Apr 2000 05:30:00 -0000	[thread overview]
Message-ID: <ptr9bu5q5p.fsf@masala.cygnus.co.uk> (raw)
In-Reply-To: <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.

WARNING: multiple messages have this Message-ID
From: Hugo 'NOx' Tyson <hmt@cygnus.co.ukx>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Problem about the uitron test
Date: Wed, 05 Sep 2001 00:09:00 -0000	[thread overview]
Message-ID: <ptr9bu5q5p.fsf@masala.cygnus.co.uk> (raw)
Message-ID: <20010905000900.TppxD-H-IlMrxagIKNoaaPX7aJWIx7qLyvGlsm8Vtok@z> (raw)
In-Reply-To: <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.

  reply	other threads:[~2000-04-25  5:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-21  2:51 pyxue
2000-04-25  5:30 ` Hugo 'NOx' Tyson [this message]
2001-09-05  0:09   ` Hugo 'NOx' Tyson

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=ptr9bu5q5p.fsf@masala.cygnus.co.uk \
    --to=hmt@cygnus.co.ukx \
    --cc=ecos-discuss@sourceware.cygnus.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).