This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: cyg_current_time () locking up
- To: "'eCos Disuss'" <ecos-discuss at sourceware dot cygnus dot com>
- Subject: RE: [ECOS] cyg_current_time () locking up
- From: "Trenton D. Adams" <tadams at theone dot dnsalias dot com>
- Date: Fri, 10 Aug 2001 09:47:47 -0600
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
-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com] On Behalf Of Trenton D.
Adams
Sent: Friday, August 10, 2001 9:40 AM
To: 'eCos Disuss'
Subject: [ECOS] cyg_current_time () locking up
This is very odd. I have a program that was working fine yesterday.
Now it locks up when I call cyg_current_time (). Below is the code that
locks up. It locks up right on cyg_current_time (). Any particular
reason why this could happen? problem in the system code maybe?
ticks = cyg_current_time ();
cyg_mutex_lock (&threadData->mutexA1);
newDataLen = GenerateWave (threadData->channelABuffer1,
&lastValue);
threadData->channelABufLen1 = newDataLen;
cyg_cond_signal (&threadData->condA1);
cyg_mutex_unlock (&threadData->mutexA1);
Trenton D. Adams
Extreme Engineering
#17, 6025 - 12 St. SE
Calgary, Alberta, Canada
T2H 2K1
Phone: 403 640 9494 ext-208
Fax: 403 640 9599
http://www.extremeeng.com