#5723: fork() doesn't ensure a consistent state of libroot data
---------------------------------+----------------------------
Reporter: bonefish | Owner: axeld
Type: bug | Status: closed
Priority: normal | Milestone: R1
Component: System/libroot.so | Version: R1/Development
Resolution: fixed | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
---------------------------------+----------------------------
Changes (by bonefish):
* status: new => closed
* resolution: => fixed
Comment:
The ticket is quite general, but since POSIX restricts, what can be done
after `fork()` anyway, I guess the status quo -- the runtime loader and
the memory allocator being safe -- should be OK.
--
Ticket URL: <https://dev.haiku-os.org/ticket/5723#comment:2>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
