This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
UITRON/threads wierdness or silliness..
- To: ecos-discuss at sources dot redhat dot com
- Subject: [ECOS] UITRON/threads wierdness or silliness..
- From: "Dave Airlie" <airlied at parthus dot com>
- Date: 23 Oct 2000 12:47:54 +0100
Hi,
I've got an application that I've recently started running with
asserts switched on :-), it uses 5 UITRON tasks with 20k stacks.
ASSERT FAIL: <7>sched.cxx [ 152] static void
Cyg_Scheduler::unlock_inner() Bad
next thread
rears its ugly head
$1 = {<Cyg_HardwareThread> = {stack_base = 270244, stack_size = 20000,
stack_limit = 270244, stack_ptr = 256024,
entry_point = 0x9950 <main_task>,
As you can see stack_ptr is pointing below stack base ...
I'm just wondering how such a thing could happen... I though it was stack
size but the assert checks stack_base + stack_size, so somehow I'm going
below my base ptr ..
it seems to happen after I trigger the first task but I'm not too
sure.. I'm going in deeper but I thought I'd ask just in case someone
spots something obvious..
any ideas?
Dave.
--
David Airlie, Software Engineer, Parthus Technologies plc.,
Mary Rosse Centre, National Tech Park, Limerick, Ireland.
t: +353-61-508116 / f: +353-61-508101 / David.Airlie@parthus.com