[haiku-commits] Re: BRANCH pdziepak-github.scheduler [24dbeed] src/system/kernel/scheduler src/system/libroot/posix/malloc headers/private/kernel

From: Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
To: haiku-commits@xxxxxxxxxxxxx
Date: Wed, 09 Oct 2013 09:15:38 +0200

Am 09/10/2013 04:15, schrieb pdziepak-github.scheduler:

3e91b08: libroot: Do not rely on thread_yield()


Out of curiosity, why was this necessary?

-       lock = UNLOCKED;
+       mutex_init(&lock, name);


Is it possible that you broke the lock on fork?

Bye,
   Axel.

Follow-Ups:
- [haiku-commits] Re: BRANCH pdziepak-github.scheduler [24dbeed] src/system/kernel/scheduler src/system/libroot/posix/malloc headers/private/kernel
  - From: Pawel Dziepak

References:
- [haiku-commits] BRANCH pdziepak-github.scheduler [24dbeed] src/system/kernel/scheduler src/system/libroot/posix/malloc headers/private/kernel
  - From: pdziepak-github . scheduler

Other related posts:

» [haiku-commits] BRANCH pdziepak-github.scheduler [24dbeed] src/system/kernel/scheduler src/system/libroot/posix/malloc headers/private/kernel- pdziepak-github . scheduler
» [haiku-commits] Re: BRANCH pdziepak-github.scheduler [24dbeed] src/system/kernel/scheduler src/system/libroot/posix/malloc headers/private/kernel - Axel Dörfler
» [haiku-commits] Re: BRANCH pdziepak-github.scheduler [24dbeed] src/system/kernel/scheduler src/system/libroot/posix/malloc headers/private/kernel- Pawel Dziepak