From: "Frank Ch. Eigler" <fche@redhat.com>
To: wei gong <gongwei833x@gmail.com>
Cc: systemtap@sourceware.org
Subject: Re: Using systemtap in an Environment with Multiple Versions of glibc
Date: Sat, 29 Jul 2023 09:16:47 -0400 [thread overview]
Message-ID: <20230729131647.GB5602@redhat.com> (raw)
In-Reply-To: <CAPqx3PETX5ZDrwjZQDQ7UjtCNahHPtXN71jjibOphLBirSkcoA@mail.gmail.com>
Hi -
> > stap --ldd -d /opt/compiler/gcc-8.2/usr/lib/libc.so.6 -d
> /opt/compiler/gcc-8.2/lib/ld-linux-x86-64.so.2 -d
> /opt/compiler/gcc-8.2/lib64/ld-linux-x86-64.so.2 -e 'probe
> process("myapp").function("func_name").call {print_ubacktrace()}'
> WARNING: module /home/opt/compiler/gcc-8.2/lib/libc-2.21.so --ldd skipped:
> unsupported interpreter: /opt/compiler/gcc-8.2/lib/ld-linux-x86-64.so.2
> WARNING: module myapp --ldd skipped: unsupported interpreter:
> /opt/compiler/gcc-8.2/lib64/ld-linux-x86-64.so.2
Ah yeah. Having a custom ld.so like that is unusual. Sorry I didn't
realize this aspect of your situation. You could try running ldd
yourself on your binary, and manually add "-d
/opt/compiler/..../lib..." flags for each.
- FChE
next prev parent reply other threads:[~2023-07-29 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 13:59 wei gong
2023-07-28 19:21 ` Frank Ch. Eigler
2023-07-29 12:46 ` wei gong
2023-07-29 13:16 ` Frank Ch. Eigler [this message]
2023-07-30 4:32 ` wei gong
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=20230729131647.GB5602@redhat.com \
--to=fche@redhat.com \
--cc=gongwei833x@gmail.com \
--cc=systemtap@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).