Fork of NextBSD's libxpc for Darling build
Go to file
Thomas A b4880a260e Only call release if message is not NULL
For some reason, launchd seems to stall when `[message release]` is called when message is NULL.

This only seems to be an issue with the newer source. The older source doesn't require this check. I'm worried that I might be overlooking an underlying issue...
2022-05-30 17:05:16 -07:00
include Add xpc_event_publisher stubs 2022-04-29 16:47:03 -07:00
internal-include/xpc Implement xpc_dictionary_get_audit_token; remove _od_rpc_call 2021-11-28 23:45:34 -05:00
scripts Add license headers everywhere and fix small issues 2021-04-22 09:18:09 -04:00
src Only call release if message is not NULL 2022-05-30 17:05:16 -07:00
test Add license headers everywhere and fix small issues 2021-04-22 09:18:09 -04:00
.gitignore Initial commit 2015-09-11 16:35:24 +02:00
.gitmodules Initial rewrite commit 2021-03-27 15:14:08 -04:00
CMakeLists.txt Use os_log for logging 2021-05-05 15:38:42 -04:00