mirror of
https://github.com/darlinghq/darlingserver.git
synced 2024-11-23 12:29:41 +00:00
9123bad915
What this means is that we no longer release and destroy Thread and Process instances when the threads and processes they manage die. Instead, we keep them alive to perform some cleanup (like finishing active calls). This should fix the duct-tape panic where threads and tasks are still referenced at death. Best of all, there don't seem to be any leaks with this approach: for each `process dying` or `thread dying` message in the log, there's a `process being destroyed` or `thread being destroyed` message later on. This means we're not leaking any processes or threads. |
||
|---|---|---|
| .. | ||
| defines | ||
| include/darlingserver | ||
| internal-include/darlingserver/duct-tape | ||
| pthread | ||
| src | ||
| xnu | ||
| CMakeLists.txt | ||
| README.md | ||
darlingserver Duct Taping
The purpose of this subproject is to use a significantly stripped down version of XNU's own kernel code coupled with some glue/duct-tape code to simulate the necessary parts of a normal XNU kernel environment for the code to work properly to implement things like Mach IPC.