[ECOS] Re: Unexpected exit from threads
Thu Nov 23 10:07:00 GMT 2006
Yes, the for loops are long enough for the leds to be
visible. I traced the cyg_thread_delay and after the
Cyg_Thread::unlock() call, nothing happens, the
execution goes to the main function.
--- Nick Garnett <firstname.lastname@example.org> wrote:
> David Luca <email@example.com> writes:
> > Hello,
> > I tried the example found in twothreads.c, but
> > the file to hello.cpp to compile it with g++.
> > I commented the printf calls and replaced with
> > lighting led functions. The code looks like:
> What happens if you leave the printf()s in as well
> as the led
> functions? Are you sure that the for loop are long
> enough for the led
> changed to be visible?
> > When I run this example, I can see that each of
> the 2
> > leds are lit, then the threads exits without
> > continuing.
> It is unlikely that the threads are exiting...
> > Is there something wrong with the
> > scheduler?
> ...or that there is anything wrong with the
> Nick Garnett
> eCos Kernel Architect
> http://www.ecoscentric.com The eCos
> and RedBoot experts
Want to start your own business?
Learn how on Yahoo! Small Business.
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
More information about the Ecos-discuss