From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 17723 invoked from network); 21 Oct 2023 00:00:15 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 21 Oct 2023 00:00:15 -0000 Received: (qmail 14149 invoked by uid 550); 21 Oct 2023 00:00:11 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 14105 invoked from network); 21 Oct 2023 00:00:10 -0000 Date: Fri, 20 Oct 2023 20:00:03 -0400 From: Rich Felker To: Farid Zakaria Cc: musl@lists.openwall.com Message-ID: <20231021000003.GO4163@brightrain.aerifal.cx> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] dynlink.c tests 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