This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Bug 1000400] ASSERT enabled build fails at startup
- From: bugzilla-daemon at ecoscentric dot com
- To: ecos-bugs at sources dot redhat dot com
- Date: Mon, 21 May 2007 14:35:26 +0100 (BST)
- Subject: [Bug 1000400] ASSERT enabled build fails at startup
https://bugzilla.ecoscentric.com/show_bug.cgi?id=1000400
jifl@ecoscentric.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |NOTABUG
------- Additional Comments From jifl@ecoscentric.com 2007-05-21 14:35 -------
If you are seeing Cyg_Thread::self==0, then that means you are calling kernel
functions (like Cyg_Mutex::lock) without the kernel having been initialised.
This is both unsupported and a bad idea.
How can I tell this? Because when the kernel scheduler initialises, it sets
Cyg_Thread::self to the idle thread.
The kernel is initialised from a bunch of prioritised C++ constructors. You must
be calling its functions from either startup HAL code or a prioritised
constructor that is called earlier than the kernel. You shouldn't do that.
--
Configure bugmail: https://bugzilla.ecoscentric.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.