This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Bad Next Thread Assertion


Hi,
I get Bad next thread assertions from Cyg_Scheduler::unlock_inner - Line 187.

I have 8 threads in my system.

All threads have the same initial code before dropping to the main loop.
They all have same priority.
The code is:
Do some HW init - currently empty body.
Set Bit in a flag (each thread sets its own bit number)
Wait to on the flag according to each thread flag_mask.
all threads have flag_mask = 0 except thread# 0 that has flag 0xFF.

When running the code I get the assertion.

When changing the priorities is works, also when adding delay in
thread# 0 between the Set Bit and the wait_flag()

Is it a known Kernel issue?

Thanks

Elad

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]