| |
On 2/28/00 11:36 AM, Martin Cornelius wrote:
> I have a 100% reproduceable way to hang my RCX during dll'ing after the
> deletion stage, and found so far that it's caught in an endless loop
> inside malloc().
For me, at least, it's not hanging during dll. My earlier problem was
that dll just wouldn't complete with my program, but it didn't crash the
RCX.
By the way, I think I've found my crashing problem. It looks like I had
some LCD calls that were happening too close together and were running
around causing problems. I added some sleep calls to space things out,
and it's running fine for now, except for how my code doesn't work, but
that's my problem. ::crosses fingers::
Are there any legOS functions that aren't thread-safe? I don't have any
indication that there are, but the idea just suddenly occured to me, and
I thought I might like to know.
--
"Every F-4 mission begins with two in-flight emergencies:
it's on fire, and it's low on fuel."
- Air Force lore
http://www.mikeash.com/ mail@mikeash.com
|
|
Message has 1 Reply:
 | | Re: Odd behavior
|
| (...) afaik, with vanilla legOS-0.2.3, lnp_addressing_write and lnp_integrity_write are not thread-safe, there is a little patch fixing this in the lnpd tarball. (25 years ago, 29-Feb-00, to lugnet.robotics.rcx.legos)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
