From: Tyson Whitehead <twhitehead@gmail.com>
To: libc-alpha@sourceware.org
Subject: Running via <ld.so> gives a different executable
Date: Fri, 26 Feb 2021 13:21:34 -0500 [thread overview]
Message-ID: <89538393-2014-85c6-2350-9f02847318a4@gmail.com> (raw)
Happened to discover that, at least under glibc 2.31, if you launch a binary via <ld.so> on linux, the proc exe link is set to <ld.so>.
This causes ps to report the program as ld.so and also breaks (at least) any Qt application that uses QCoreApplication::applicationDirPath()
https://doc.qt.io/qt-5/qcoreapplication.html#applicationDirPath
Reaching out to the mailing list to see if this is I should be opening a bug report about?
Thanks! -Tyson
PS: Discovered this trying to use <ld.so> --preload on a Qt binary where I couldn't use LD_PRELOAD as it would pollute the forked children.
next reply other threads:[~2021-02-26 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 18:21 Tyson Whitehead [this message]
2021-02-26 19:23 ` Andreas Schwab
2021-02-26 21:08 ` Tyson Whitehead
2021-02-26 21:23 ` Andreas Schwab
2021-02-26 21:53 ` Tyson Whitehead
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=89538393-2014-85c6-2350-9f02847318a4@gmail.com \
--to=twhitehead@gmail.com \
--cc=libc-alpha@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).