Re: rtld: Relocation from unversioned binary matches oldest version instead of "default"

On Fri, May 13, 2022 at 01:16:39PM +0200, obiwac wrote: > Wassup, > > This may not be strictly speaking a bug with rtld, but it sure is > weird/awkward behaviour considering the existing information I could > gather. > > In an unversioned shared object which references a symbol which has >

Re: Chasing OOM Issues - good sysctl metrics to use?

On 5/11/22 12:52, Mark Millard wrote: Relative to avoiding hang-ups, so far it seems that use of vm.swap_enabled=0 with vm.swap_idle_enabled=0 makes hang-ups less likely/less frequent/harder to produce examples of. But is no guarantee of lack of a hang-up. Its does change the cause of the

rtld: Relocation from unversioned binary matches oldest version instead of "default"

Wassup, This may not be strictly speaking a bug with rtld, but it sure is weird/awkward behaviour considering the existing information I could gather. In an unversioned shared object which references a symbol which has multiple versions (e.g. readdir@@FBSD_1.5 & readdir@FBSD_1.0, found with