Date: Mon, 23 Oct 2023 10:08:41 -0700 From: Farid Zakaria <fmzakari@...c.edu> To: Rich Felker <dalias@...c.org> Cc: musl@...ts.openwall.com Subject: Re: dynlink.c tests Sorry for the late reply Rich. That's what my current plan of attack is but I was wondering if the musl codebase itself has such a test suite already (something similar to the libc test suite) How do dynlink authors validate they haven't broken any edge cases in program loading? (i.e. such as DT_GNU_HASH etc..) On Fri, Oct 20, 2023 at 5:00 PM Rich Felker <dalias@...c.org> wrote: > > On Fri, Oct 20, 2023 at 11:18:44AM -0700, Farid Zakaria wrote: > > What's the best way to test dynlink.c ? > > I'm making some small changes (actually just simplifying it by > > removing some code for unneeded arch like DL_FDPIC) but would like to > > make sure I didn't bork anything. > > > > I found https://wiki.musl-libc.org/writing-tests but that seems > > focused strictly on the libc itself. > > Is there a dynamic-loader test suite anyone is familiar with ? > > The general strategy I would use would be to setup recipes to build > binaries/shared libraries that make use of particular dynamic linking > features, then load/execute them in ways that assert that the relevant > feature operated as expected. > > Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.