This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
Re: twothreads.c not working correctly on ARM AEB1
- To: javelina <javelina at home dot com>
- Subject: Re: [ECOS] twothreads.c not working correctly on ARM AEB1
- From: Jonathan Larmour <jlarmour at redhat dot co dot uk>
- Date: Tue, 13 Jun 2000 16:03:32 +0100
- CC: ecos-discuss at sourceware dot cygnus dot com
- Organization: Red Hat UK Ltd.
- References: <3945AF98.2C962EAD@home.com>
javelina wrote:
> Continuing.
> Entering twothreads' cyg_user_start() function
> Beginning execution; thread data is 0
> Beginning execution; thread data is 1
> Thread 0: and now a delay of 1104334939 clock ticks
> Thread 1: and now a delay of 1149184530 clock ticks
>
> Notice the HUGE delay. It should be something between 200 and 250.
I haven't seen this before. Is this the default configuration? If not,
check what differs from the default. Also enable assertions (just in case
it catches something) and also tracing so you can see if there's some
problem with the per-thread data that rand() obtains from the kernel, for
example.
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault