Re: [ECOS] cyg_current_time () locking up

[Hugo Tyson <hmt at redhat dot com>]

Grant Edwards <grante@visi.com> writes:
> On Fri, Aug 10, 2001 at 05:50:46PM +0200, Andrew Lunn wrote:
> > On Fri, Aug 10, 2001 at 09:47:47AM -0600, Trenton D. Adams wrote:
> 
> > > Nope, that's not what's locking it up.  I get the error below after
> > > fiddling with some of the code.  What does it mean?
> > > 
> > > ASSERT FAIL: <2>[166]static void Cyg_Scheduler::unlock_inner() Bad next
> > > thread
> > 
> > At a guess, you have a stack overflow which has corrupted something
> > important in one of your threads. Try making your stacks bigger.
> 
> I don't remember seeing the choice, but does eCos have an
> option to check for stack overflows

See the option CYGFUN_KERNEL_ALL_THREADS_STACK_CHECKING.

> It didn't catch every case of stack overflow since it was still
> possible for the program to blow up irreperably before the next
> context switch or timer interrupt, but it caught enough
> problems to be useful.

Indeed, that's the reality of it.

	- Huge