public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29539] New: LD_TRACE_LOADED_OBJECTS changed how vDSO library are printed
Date: Tue, 30 Aug 2022 16:35:40 +0000	[thread overview]
Message-ID: <bug-29539-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29539

            Bug ID: 29539
           Summary: LD_TRACE_LOADED_OBJECTS changed how vDSO library are
                    printed
           Product: glibc
           Version: 2.36
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: adhemerval.zanella at linaro dot org
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

The d7703d3176d225d5743b21811d888619eba39e82 changed on how vDSO like
dependencies are printed, instead of just the name and address it follows other
libraries mode and print 'name => path'.

Unfortunately, this broke some ldd consumer that uses the output to filter out
the program's dependencies.  For instance CMake bundleutilities module [1],
where GetPrequirite uses the regex to filter out 'name => path' [2].

[1] https://github.com/Kitware/CMake/tree/master/Tests/BundleUtilities
[2]
https://github.com/Kitware/CMake/blob/master/Modules/GetPrerequisites.cmake#L733

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-08-30 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 16:35 adhemerval.zanella at linaro dot org [this message]
2022-08-31 12:09 ` [Bug libc/29539] " adhemerval.zanella at linaro dot org

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-29539-131@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: link
Be 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).