From: wei gong <gongwei833x@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: Using systemtap in an Environment with Multiple Versions of glibc
Date: Sun, 30 Jul 2023 12:32:30 +0800 [thread overview]
Message-ID: <CAPqx3PG4vqJG=nCAMyof6uz+khibjzExiXRaxRm5RFPE+ez7Ug@mail.gmail.com> (raw)
In-Reply-To: <20230729131647.GB5602@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]
Hi
> 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.
>
> I tried running ldd on my binary file and manually adding ‘-d
/opt/compiler/…/lib…’ for each one.
stap -d /opt/compiler/gcc-8.2/usr/lib/libpixman-1.so.0 -d
/opt/compiler/gcc-8.2/usr/lib/libz.so.1 -d
/opt/compiler/gcc-8.2/usr/lib/libutil.so.1 -d
/opt/compiler/gcc-8.2/usr/lib/libglib-2.0.so.0 -d
/opt/compiler/gcc-8.2/usr/lib/libdl.so.2 -d
/opt/compiler/gcc-8.2/usr/lib/libcurl.so.4 -d
/opt/compiler/gcc-8.2/usr/lib/libaio.so.1 -d
/opt/compiler/gcc-8.2/usr/lib/libstdc++.so.6 -d
/opt/compiler/gcc-8.2/usr/lib/libgflags.so.2.1 -d
/opt/compiler/gcc-8.2/usr/lib/libprotobuf.so.8 -d
/opt/compiler/gcc-8.2/usr/lib/libleveldb.so.1 -d
/opt/compiler/gcc-8.2/usr/lib/libm.so.6 -d
/opt/compiler/gcc-8.2/usr/lib/libgcc_s.so.1 -d
/opt/compiler/gcc-8.2/usr/lib/libpthread.so.0 -d
/opt/compiler/gcc-8.2/usr/lib/libc.so.6 -d
/opt/compiler/gcc-8.2/usr/lib/libpcre.so.1 -d
/opt/compiler/gcc-8.2/usr/lib/libsnappy.so.1 -d
/opt/compiler/gcc-8.2/lib64/ld-linux-x86-64.so.2 -e 'probe
process("myapp").function("function").call {print_ubacktrace()}'
Trigger probe point function
WARNING: Missing unwind data for a module, rerun with 'stap -d (unknown;
retry with -DDEBUG_UNWIND)'
0x8789b6
Best Regards,
WeiGong
prev parent reply other threads:[~2023-07-30 4:32 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
2023-07-30 4:32 ` wei gong [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='CAPqx3PG4vqJG=nCAMyof6uz+khibjzExiXRaxRm5RFPE+ez7Ug@mail.gmail.com' \
--to=gongwei833x@gmail.com \
--cc=fche@redhat.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).