Lines Matching refs:this
26 // state and have been doing so for a long time. Regardless the comments in this function shall
32 // MT programs provided the only way a program used dl* was via this library. However, it also
58 // In non-dlsym case this may happen when there’re bugs in our bindings or there’s
82 // That being said... this section in the volume 2 of POSIX.1-2008 states:
84 // > All functions defined by this volume of POSIX.1-2008 shall be thread-safe, except that the
87 // With notable absence of any dl* function other than dlerror in the list. By “this volume”
89 // by this same volume, so the conclusion is indeed that dl* functions are required by POSIX
116 /// Additionally, the callers of this function must also ensure that execution of the
134 /// Note that the behaviour of a `Library` loaded with this method is different from that of
135 /// Libraries loaded with [`os::windows::Library::this`].
139 /// [`os::windows::Library::this`]: crate::os::windows::Library::this
141 pub fn this() -> Library {
143 // SAFE: this does not load any new shared library images, no danger in it executing
145 Library::open(None::<&OsStr>, RTLD_LAZY | RTLD_LOCAL).expect("this should never fail")
151 /// See documentation for [`Library::this`] for further description of the behaviour
163 /// Additionally, the callers of this function must also ensure that execution of the
195 // pointer or the symbol cannot be found. In order to detect this case a double dlerror
198 // We try to leave as little space as possible for this to occur, but we can’t exactly
229 /// Users of this API must specify the correct type of the function or variable loaded. Using a
238 /// as FreeBSD), this function will unconditionally return an error when the underlying `dlsym`
275 /// Users of this API must specify the correct type of the function or variable loaded.
277 /// It is up to the user of this library to ensure that no other calls to an MT-unsafe
278 /// implementation of `dlerror` occur during the execution of this function. Failing that, the
279 /// behaviour of this function is not defined.
295 /// The handle returned by this function shall be usable with APIs which accept handles
309 /// with this pointer as an argument.
321 /// You only need to call this if you are interested in handling any errors that may arise when
336 // this time it would ignore the return result, which we already seen failing…
358 /// A major difference compared to the cross-platform `Symbol` is that this does not ensure that the