Re: [lwip-users] Debug code

[Henrik Ripa]

--- Leon Woestenberg <address@hidden> wrote:
> This is not generally true. If the OS can switch tasks pre-emptively, and
> printf does not
> lock the scheduler, the printf()ing task can simply be switched from the CPU
> and a new
> printf()ing task can be switched in.
> 
> I have solved this by having DEBUGF lock the scheduler, call printf(),
> unlock the scheduler.

Excuse a newbie, but shouldn't debug-information be printed to std_err so
that it becomes flushed out directly? It sounds like overkill to lock the
scheduler for such a trvivial task. I'm probably wrong but I was just
wondering.


=====
Henrik Ripa [Gieron] - Lule/Norrbotten/Sweden

__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/