Re: [ECOS] cyg_current_time () locking up

[Andrew Lunn <andrew dot lunn at ascom dot ch>]

On Fri, Aug 10, 2001 at 09:55:41AM -0600, Trenton D. Adams wrote:
> Thanks! :)
> 
> How did you come to that conclusion anyhow?

It was code that you said worked before, but does not now.
cyg_current_time() is not something i would expect to go wrong. This
makes me think its something else. From experiance, the normal
something else which causes this assertion failure is stack overflow.
Been there, done that, know what to look for now.

        Andrew
 
> -----Original Message-----
> From: Andrew Lunn [mailto:andrew.lunn@ascom.ch] 
> Sent: Friday, August 10, 2001 9:51 AM
> To: Trenton D. Adams
> Cc: 'eCos Disuss'
> Subject: Re: [ECOS] cyg_current_time () locking up
> 
> 
> 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.
> 
>         Andrew
>