public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/15311] _dl_sort_fini static deps can be violated by dynamic ones Date: Thu, 21 Oct 2021 19:21:18 +0000 [thread overview] Message-ID: <bug-15311-131-RvWnpn6sHR@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15311-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15311 --- Comment #10 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Adhemerval Zanella <azanella@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=e6fd79f3795d46dfb583e124be49fc063bc3d58b commit e6fd79f3795d46dfb583e124be49fc063bc3d58b Author: Chung-Lin Tang <cltang@codesourcery.com> Date: Thu Oct 21 21:41:21 2021 +0800 elf: Testing infrastructure for ld.so DSO sorting (BZ #17645) This is the first of a 2-part patch set that fixes slow DSO sorting behavior in the dynamic loader, as reported in BZ #17645. In order to facilitate such a large modification to the dynamic loader, this first patch implements a testing framework for validating shared object sorting behavior, to enable comparison between old/new sorting algorithms, and any later enhancements. This testing infrastructure consists of a Python script scripts/dso-ordering-test.py' which takes in a description language, consisting of strings that describe a set of link dependency relations between DSOs, and generates testcase programs and Makefile fragments to automatically test the described situation, for example: a->b->c->d # four objects linked one after another a->[bc]->d;b->c # a depends on b and c, which both depend on d, # b depends on c (b,c linked to object a in fixed order) a->b->c;{+a;%a;-a} # a, b, c serially dependent, main program uses # dlopen/dlsym/dlclose on object a a->b->c;{}!->[abc] # a, b, c serially dependent; multiple tests generated # to test all permutations of a, b, c ordering linked # to main program (Above is just a short description of what the script can do, more documentation is in the script comments.) Two files containing several new tests, elf/dso-sort-tests-[12].def are added, including test scenarios for BZ #15311 and Redhat issue #1162810 [1]. Due to the nature of dynamic loader tests, where the sorting behavior and test output occurs before/after main(), generating testcases to use support/test-driver.c does not suffice to control meaningful timeout for ld.so. Therefore a new utility program 'support/test-run-command', based on test-driver.c/support_test_main.c has been added. This does the same testcase control, but for a program specified through a command-line rather than at the source code level. This utility is used to run the dynamic loader testcases generated by dso-ordering-test.py. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1162810 Signed-off-by: Chung-Lin Tang <cltang@codesourcery.com> Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org> -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2021-10-21 19:21 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-27 7:49 [Bug dynamic-link/15311] New: " dhatch at ilm dot com 2013-03-27 8:46 ` [Bug dynamic-link/15311] " dhatch at ilm dot com 2013-03-27 12:59 ` carlos at redhat dot com 2013-03-27 20:35 ` dhatch at ilm dot com 2013-03-27 22:09 ` neleai at seznam dot cz 2013-03-27 22:09 ` [Bug dynamic-link/15311] New: " Ondřej Bílka 2013-03-27 22:40 ` [Bug dynamic-link/15311] " dhatch at ilm dot com 2013-03-28 4:36 ` dhatch at ilm dot com 2013-03-28 5:00 ` dhatch at ilm dot com 2013-03-28 7:37 ` Ondřej Bílka 2013-03-28 7:37 ` neleai at seznam dot cz 2013-03-28 8:19 ` Ondřej Bílka 2013-03-28 8:19 ` neleai at seznam dot cz 2013-03-29 14:53 ` dhatch at ilm dot com 2014-06-13 18:36 ` fweimer at redhat dot com 2021-10-21 19:21 ` cvs-commit at gcc dot gnu.org [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-15311-131-RvWnpn6sHR@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).