From: Farid Zakaria <fmzakari@ucsc.edu>
To: Libc-help <libc-help@sourceware.org>
Subject: LD_AUDIT shared object using multiple object files
Date: Sat, 30 Apr 2022 19:16:17 -0700 [thread overview]
Message-ID: <CAH4OOv7beAFMhD8+xZa=NLJ=ucPTJOw7tYD9KHZPbz6m2XN5AQ@mail.gmail.com> (raw)
Hello!
I am trying to write a small problem to leverage the rtld audit[1] API
however I am running into an issue I am not sure I understand.
When I have restricted my program to a single object file (compilation
unit), everything works _peachy_. I am able to set LD_AUDIT
accordingly and things work as I expect.
I then try to refactor my code into smaller object files (trying to be
a good code citizen), but then the solution stopped working.
I am greeted with some "unresolved symbol" messages for the new
compilation units.
Is there a way around this?
PS: I also built a binary and verified that everything works
correctly, since my main() runs successfully, so my code structure is
sound as far as I can tell.
[1] https://man7.org/linux/man-pages/man7/rtld-audit.7.html
next reply other threads:[~2022-05-01 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 2:16 Farid Zakaria [this message]
2022-05-01 7:07 ` Florian Weimer
2022-05-02 17:13 ` Farid Zakaria
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='CAH4OOv7beAFMhD8+xZa=NLJ=ucPTJOw7tYD9KHZPbz6m2XN5AQ@mail.gmail.com' \
--to=fmzakari@ucsc.edu \
--cc=libc-help@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).