 | | Semaphore(s) locked when task killed. —Joseph Woolley
|
| | | 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: Semaphore(s) locked when task killed. —Mark Falco
|
| | | | | (...) 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)
|
| | | | | |
| | | | | Re: Semaphore(s) locked when task killed. —Steve Hassenplug
|
| | | | | (...) 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. —Joseph Woolley
|
| | | | | | Last night I worked on a solution to this. So far it is coming along very good. My proposed solution is to write tasks so that they shutdown when signalled. The user tasks should respond to the run/stop button by shutting down gracefully. If a task (...) (22 years ago, 5-Sep-02, to lugnet.robotics.rcx.legos)
|
| | | | | | |
| | | | | Re: Semaphore(s) locked when task killed. —Albert Huang
|
| | | | | 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. —Joseph Woolley
|
| | | | | | This has been suggested and may very well be the best way to handle manual removal of a runaway task. I plan to investigate this once I get my current updates squared-away. I hope this type of handling can be done in the kernel only. User tasks (...) (22 years ago, 5-Sep-02, to lugnet.robotics.rcx.legos)
|
| | | | | | |
| | | | | Re: Semaphore(s) locked when task killed. —Joseph Woolley
|
| | | | I have completed an update to solve some of the problems mentioned previously. If all goes well, I will be able to start updating the files on sourceforge within a week. More soon. // Joe (22 years ago, 9-Sep-02, to lugnet.robotics.rcx.legos)
|
| | | | |
