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.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, 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 29273 invoked from network); 23 Oct 2023 17:09:11 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 23 Oct 2023 17:09:11 -0000 Received: (qmail 11812 invoked by uid 550); 23 Oct 2023 17:09:06 -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 11746 invoked from network); 23 Oct 2023 17:09:05 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google-2018; t=1698080932; x=1698685732; darn=lists.openwall.com; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=DhzEZQM1o/J5S6rv9sEir8XTmQfDeatrSHS77EjtIXU=; b=LRHe1qH44Ne4rbMmWDUc2Piupiz0gZh0k4JwTU5V2JNZzunwXI2JfN7UNc/7Q7PIAo /Ti6q9O2sJr7H4WmylNs8h9NnWi20ywExoVvYQJ0wxW4LiUhhyuJ2qrdEDlp7RZLQRtd dyU2L4Du5CXWb1FR9H0B1FuMibZWojWnh/AUN6YfelNRVbvramJVHcl01GNWqEFR3iYd 7xkGpe9uiFabC17BE9eGYklK7OOCGiHhePbmvkDco19vs7ss8LjRLUucs0hY0mWhw9H6 wkz82/ArGdJaUhVHAoGl/MTV5bEZgjgSA9jXGwB1f9LYgqp5HTkiuxs0ieX5Cjs0okQE BCLg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698080932; x=1698685732; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=DhzEZQM1o/J5S6rv9sEir8XTmQfDeatrSHS77EjtIXU=; b=KrUJgovPV0TNdyszOf3Ut9XnPnow6yHCwTV2JSAFV9eSI2i/ShHOOf5DDSr06wPaYF losx4JYXzQaKENhfRWCyZwCWR2GlLASVNyAH51BSlpalpE95JH9+RrJQYIRQ/mDZhN3V 1rDdQIs9/bUkj1zXT24Q1bFIm6ZuQKKeG0aA54M79lEaLAGIw1BzCiOR0ySDINyxA/dy gQNM7N0OXiE/V+3R7+0ZbWCtpv1/QDCSHfzU0lx5oNfFGF1clEQ74sMRLGz7IXZxlol9 63QZbVZGK59SvLSJyVVyKzj6ImUl4PgYcBSPu8yVRlrOIknUfdni56fLhB8Ak2czUntG 8aqw== X-Gm-Message-State: AOJu0YyKZCxBxOi29bAFSSlTx7prpQz1m9ptL0vTRnbxq9E/NtyQ/0WQ p7eYdAzrg/myl9xxn+P5rXLqSuQI7Pge0P7VCypqPg== X-Google-Smtp-Source: AGHT+IFpj0fX55VQJx+Y/OxYoj6BEzzsdvPUvV0XVhQyZzK2kmbP/HpTuno666gFbIwOu4lBgPEegWMS1nIKmkOqSk8= X-Received: by 2002:a17:90b:1117:b0:27d:5946:5e27 with SMTP id gi23-20020a17090b111700b0027d59465e27mr10324917pjb.0.1698080932025; Mon, 23 Oct 2023 10:08:52 -0700 (PDT) MIME-Version: 1.0 References: <20231021000003.GO4163@brightrain.aerifal.cx> In-Reply-To: <20231021000003.GO4163@brightrain.aerifal.cx> From: Farid Zakaria Date: Mon, 23 Oct 2023 10:08:41 -0700 Message-ID: To: Rich Felker Cc: musl@lists.openwall.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [musl] 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=E2=80=AFPM Rich Felker 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