From: "Trenton D. Adams" <tadams@theone.dnsalias.com>
To: "'eCos Disuss'" <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] cyg_current_time () locking up
Date: Fri, 10 Aug 2001 08:47:00 -0000 [thread overview]
Message-ID: <001d01c121b3$cdd86ca0$090110ac@TRENT> (raw)
In-Reply-To: <001501c121b2$a7274af0$090110ac@TRENT>
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
next prev parent reply other threads:[~2001-08-10 8:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-10 8:39 Trenton D. Adams
2001-08-10 8:47 ` Trenton D. Adams [this message]
2001-08-10 8:50 ` Andrew Lunn
2001-08-10 8:55 ` Trenton D. Adams
2001-08-10 9:01 ` Andrew Lunn
2001-08-10 9:17 ` Grant Edwards
2001-08-10 9:35 ` Hugo Tyson
2001-08-10 9:51 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001d01c121b3$cdd86ca0$090110ac@TRENT' \
--to=tadams@theone.dnsalias.com \
--cc=ecos-discuss@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).