 | | Re: Semaphore(s) locked when task killed.
|
|
Have you considered implementing thread cleanup handlers? Similar to what pthread_cleanup_push and pthread_cleanup_pop provide. "Joseph Woolley" <jwoolley@spamblock....ht.rr.com> wrote in message news:H1w6v9.8M0@lugnet.com... (...) tasks. (...) task (...) (22 years ago, 4-Sep-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Semaphore(s) locked when task killed.
|
|
(...) This explains a problem I've been having. I've noticed this exact issue, but I wasn't sure if I was doing something wrong, or exactly what the problem was. I have a program that sends IR messages (for proximity) and after the program is (...) (22 years ago, 4-Sep-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Semaphore(s) locked when task killed.
|
|
(...) hmmm I wonder what other unix like OSs do in this situation? automatically unlocking doesn't seem particuarlly clean, what is to say that it is safe to unlock the mutexes just because the locking thread has been killed? Perhaps we can (...) (22 years ago, 4-Sep-02, to lugnet.robotics.rcx.legos)
|
| |
| | Semaphore(s) locked when task killed.
|
|
I have found that killing a task which is sending data via lnp will cause lnp to stop functioning. Turning the brick off then on again will get lnp working again. The issue is with the semaphore(s) used in the kernel tasks. Currently there is no (...) (22 years ago, 4-Sep-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Small problem compiling w/gcc-3.2 and binutils-2.12.0 with patch.
|
|
John, Good Job, John! It seems that older version of gcc don't catch the problem. I applied the changes and it compiles fine for me; I updated CVS. // Joe "John Jorgensen" <jjorgens@2gn.com> wrote in message news:Pine.LNX.4.21.0...2gn.com... (...) (...) (22 years ago, 4-Sep-02, to lugnet.robotics.rcx.legos)
|
| |
| | Small problem compiling w/gcc-3.2 and binutils-2.12.0 with patch.
|
|
While compiling the brickos kernel under gcc-3.2 and binutils-2.12.0 I was getting errors about nb_tasks and nb_system_tasks not being te same as their declarations so I made them volatile just like in the header and the kernel now compiles. The (...) (22 years ago, 3-Sep-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Legos or Lejos
|
|
(...) If you already know some Java, I recommend Lejos. It has some very reliable classes for RCX to RCX communications using Java streams. It also has some useful debugging features. Good luck, Roger (22 years ago, 3-Sep-02, to lugnet.robotics.rcx.java, lugnet.robotics.rcx.legos)
|
| |
| | Re: binutils 2.12 is the last one to work
|
|
(...) yes, that's possible, but isn't the symbolsrec format a bit of a standard, indicating that the 2.12.1 version is just buggy? Also, it doesn't help with 2.13 since that one doesn't even get to produce any code. alejandro (22 years ago, 2-Sep-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: binutils 2.12 is the last one to work Re: was compile error (was link error with binutils 2.13)
|
|
(...) You are right. I have the 2.12.1 rpm in my package folder and assumend that it is the one I use. But asking ld for it's version resulted in 2.12. One way ist to stay with 2.12, a second way is to change makelx so it could handle the (...) (22 years ago, 2-Sep-02, to lugnet.robotics.rcx.legos)
|
| |
| | Release candidate brickos-0.2.6.07 avail for testing
|
|
This is our first public visible test version since the name change. It is also the first in what will be a series of test releases. We will announce when we think we are closing in on the actual release. Details regarding test release content, (...) (22 years ago, 2-Sep-02, to lugnet.robotics.rcx.legos)
|
