←back to thread

Why did dlclose not unload the library? (2023)

(kishoreganesh.com)
39 points mattrighetti | 1 comments | 27 Aug 25 00:45 UTC | HN request time: 0.201s | source
Show context
sgbeal ◴[30 Aug 25 13:34 UTC] No.45074556[source]▶
There is no safe, reliable, cross-environment way to deal with closing a DLL. A DLL initialization function can allocate arbitrary resources, some of which may be in use by clients of the DLL when it is closed.

The only safe, consistent, reliable approach is not to close DLLs.

replies(6): >>45074649 #>>45074720 #>>45075478 #>>45075558 #>>45075726 #>>45080214 #
1. dataflow ◴[30 Aug 25 15:29 UTC] No.45075478[source]▶
I feel like I wouldn't frame it like this. Rather, the underlying assumption of the problem has to be that the DLL's resources are already released, otherwise the problem of what happens when the resources are used afterward is itself ill-posed. The problem is really how to ensure that.