On Thu Jan 24, 2008 at 11:13:40 +0100, Marc CHALAND wrote:
2008/1/24, Adam Lackorzynski [EMAIL PROTECTED]:
No, the thread is still alive, the '(deleted)' just means that it has
already been unregistered at the name service.
Name service data is stored into fiasco data to be shown into
2008/1/24, Adam Lackorzynski [EMAIL PROTECTED]:
No, the thread is still alive, the '(deleted)' just means that it has
already been unregistered at the name service.
Name service data is stored into fiasco data to be shown into jdb ?
Could you verify the theory that the threadlib has some
Hi Adam all,
here the calling graph, which seems to cause the issue:
lib/src/exit.c: __do_exit () the state is set to TCB_SHUTDOWN
Afterwards the thread in shutdown progress calls __do_cleanup_and_block() -
l4th_stack_free -
l4th_pages_free -
l4rm_detach () -
l4rm_lock_region_list() -
Hi,
forgot this: after the l4lock_lock of course also a l4lock_unlock is
called (3 lines after l4lock_lock). So the thread is also dequeued from
the wait queue of the lock and so no (indirect) association to the
l4th_tcb_t data structure are hold anymore by the lock/sem. implementation.
Alex
2008/1/22, Adam Lackorzynski [EMAIL PROTECTED]:
The thread should exist, looking at the code path in the semaphore lib.
The thread_id used for the prio-get is coming fron an ipc-wait so the
thread should be there (in the sense there's a thread at all). The
thread-lib might have some other
Here is some more info about this log :
Each time this log appears, the state of the thread into jdb is, for example :
17.0d (deleted)a0 17.01 rcv,ipc_progr
Backtrace of each thread is mainly :
l4rm_detach
l4th_pages_free
__do_cleanup_and_block
We observed one thread with the
On Wed Jan 23, 2008 at 11:39:49 +0100, Marc CHALAND wrote:
2008/1/22, Adam Lackorzynski [EMAIL PROTECTED]:
The thread should exist, looking at the code path in the semaphore lib.
The thread_id used for the prio-get is coming fron an ipc-wait so the
thread should be there (in the sense
Hi,
Sometimes, I get the following message :
semaphore/lib/src/semaphore.c:167:__enqueue_thread():
Error : l4semahore: failed to get priority of thread 17.08: invalid
argument (-3)
Into sources, the comment says that thread has not been created by
l4thread or is dead.
But all threads are
Hi,
On Tue Jan 22, 2008 at 15:42:55 +0100, Marc CHALAND wrote:
Sometimes, I get the following message :
semaphore/lib/src/semaphore.c:167:__enqueue_thread():
Error : l4semahore: failed to get priority of thread 17.08: invalid
argument (-3)
Into sources, the comment says that thread has
