From: Farid Zakaria <fmzakari@ucsc.edu>
To: Florian Weimer <fweimer@redhat.com>
Cc: Farid Zakaria via Libc-help <libc-help@sourceware.org>
Subject: Re: LD_AUDIT shared object using multiple object files
Date: Mon, 2 May 2022 10:13:01 -0700 [thread overview]
Message-ID: <CAH4OOv40ByH0BZN0=oxj6J7cz3zSEGKQxZmO6eOKBjkjZoz5kA@mail.gmail.com> (raw)
In-Reply-To: <878rrlbuja.fsf@oldenburg.str.redhat.com>
I was doing something very silly and solved it.
I had mis-configured something in my build process.
I am sorry for the needless e-mail and thank you Florian for taking
the time to have read it nonetheless.
FZ
On Sun, May 1, 2022 at 12:07 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * Farid Zakaria via Libc-help:
>
> > 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?
>
> This problem doesn't sound very audit-related. You'll have to provide
> more details for what you are doing.
>
> Thanks,
> Florian
>
prev parent reply other threads:[~2022-05-02 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 2:16 Farid Zakaria
2022-05-01 7:07 ` Florian Weimer
2022-05-02 17:13 ` Farid Zakaria [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='CAH4OOv40ByH0BZN0=oxj6J7cz3zSEGKQxZmO6eOKBjkjZoz5kA@mail.gmail.com' \
--to=fmzakari@ucsc.edu \
--cc=fweimer@redhat.com \
--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).