Hello,
Sergio Lopez, le Fri 14 May 2010 12:35:41 +0200, a écrit :
> The original WAIT_DEBUG code in libthreads records the
> thread which is holding the lock, but this is not really usefull in
> Hurd's translators, since that thread is probably waiting for another
> message just as everyone else,
Sergio Lopez, le Thu 20 May 2010 00:37:48 +0200, a écrit :
> El Wed, 19 May 2010 16:27:07 +0200
> Samuel Thibault escribió:
>
> > Hello,
> >
> > Sergio Lopez, le Fri 14 May 2010 12:35:41 +0200, a écrit :
> > > I've preferred to create a new definition conditional instead of
> > > using WAIT_DEBU
El Wed, 19 May 2010 16:27:07 +0200
Samuel Thibault escribió:
> Hello,
>
> Sergio Lopez, le Fri 14 May 2010 12:35:41 +0200, a écrit :
> > I've preferred to create a new definition conditional instead of
> > using WAIT_DEBUG, since this one changes cproc_t structure size.
>
> Mmm, I don't think i
Hello,
Sergio Lopez, le Fri 14 May 2010 12:35:41 +0200, a écrit :
> I've preferred to create a new definition conditional instead of using
> WAIT_DEBUG, since this one changes cproc_t structure size.
Mmm, I don't think it'd be a problem, since the cproc_t structure is not
exposed to users of libt
Hi,
It seems that some code paths in libdiskfs still leave a mutex locked
somewhere. The original WAIT_DEBUG code in libthreads records the
thread which is holding the lock, but this is not really usefull in
Hurd's translators, since that thread is probably waiting for another
message just as ever
