Page MenuHomeFreeBSD

rtld: add some dlopen tests
ClosedPublic

Authored by kevans on Feb 13 2024, 2:31 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jun 28, 3:30 AM
Unknown Object (File)
Mon, Jun 24, 5:26 AM
Unknown Object (File)
Sat, Jun 22, 2:22 PM
Unknown Object (File)
Tue, Jun 11, 3:53 PM
Unknown Object (File)
Thu, May 30, 3:24 PM
Unknown Object (File)
May 27 2024, 10:42 AM
Unknown Object (File)
May 27 2024, 10:42 AM
Unknown Object (File)
May 27 2024, 10:42 AM
Subscribers

Details

Summary

dlopen_basic just tests that libthr.so can be dlopen()ed, which will
just serve as a sanity check that "libthr.so" is a thing that can be
dlopened in case we get a weird failure in dlopen_recursing.

dlopen_recursing tests a regression reported after the libsys split,
where some dlopen() may cause infinite recursion and a resulting crash.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

How fresh are processes where ATF executes tests? Would both dlopen_basic and dlopen_recursing execute in the same image sequentially, or ATF spawns/execs a new process to run each test?

In D43859#1000568, @kib wrote:

How fresh are processes where ATF executes tests? Would both dlopen_basic and dlopen_recursing execute in the same image sequentially, or ATF spawns/execs a new process to run each test?

Each individual test case within a program will always be executed in a fresh image -- ATF doesn't have any way to request multiple tests in a single execution of the test program

This revision is now accepted and ready to land.Feb 13 2024, 4:08 AM
This revision was automatically updated to reflect the committed changes.