Post

Replies

Boosts

Views

Activity

Reply to Incorrect behaviour of task_info() syscall after an unrelated dlclose() call
Thanks Quinn, Currently the issue doesn't seem to reproduce on latest macOS (15.5), it seems to be specific to 15.4.1. However, even though it seems to be fixed in newer builds, from what I understand, for future-proofing it is generally not recommended to use dlclose() on libraries like libswiftDemangle.dylib even though I had manually dlopen()'ed previously, and keep such libraries loaded until the application exits?
Jun ’25
Reply to Incorrect behaviour of task_info() syscall after an unrelated dlclose() call
Thanks Quinn, Currently the issue doesn't seem to reproduce on latest macOS (15.5), it seems to be specific to 15.4.1. However, even though it seems to be fixed in newer builds, from what I understand, for future-proofing it is generally not recommended to use dlclose() on libraries like libswiftDemangle.dylib even though I had manually dlopen()'ed previously, and keep such libraries loaded until the application exits?
Replies
Boosts
Views
Activity
Jun ’25
Reply to Incorrect behaviour of task_info() syscall after an unrelated dlclose() call
Thanks a lot Kevin and Quinn, Greatly appreciate your detailed responses!
Replies
Boosts
Views
Activity
Jul ’25