From: Ramesh Errabolu via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: [lttng-dev] Can't trace function calls
Date: Wed, 31 Mar 2021 10:51:03 -0500 [thread overview]
Message-ID: <CAFGSPrw1Ev1c+Ok7tvyzEJOQNDze6fbpzNKFzmH=9hSVYGF69A@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1086 bytes --]
I am trying to capture the list of functions being called by an app. The
app relies on a couple of shared libraries (libhsa-runtime64.so and
libhsakmt.so).
My experiments all *FAIL *i.e. there are no log files of the output. The
link on lttng-ust-cyg-profile does not tell me where I can get them.
Instrument the build files for the two libraries to allow function tracing
by the gcc/clang flags -finstrument-functions and run workload as follows
- Instrument the build files for the two libraries to allow function
tracing by the gcc/clang flags *-finstrument-functions* and run workload
as follows
- LD_PRELOAD=liblttng-ust-cyg-profile.so ./rocminfo
- Instrument the application as well for the gcc/clang flag along with
the two libs
- LD_PRELOAD=liblttng-ust-cyg-profile.so ./rocminfo
I am using LTTng version Ubuntu: LTTng Stable 2.12 PPA
- apt-get install lttng-tools
- apt-get install lttng-modules-dkms
- apt-get install liblttng-ust-dev
I noticed no kernel modules with substring "ltt" in it.
Any help is appreciated.
Regards,
Ramesh
[-- Attachment #1.2: Type: text/html, Size: 1937 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2021-03-31 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 15:51 Ramesh Errabolu via lttng-dev [this message]
2021-03-31 17:42 ` [lttng-dev] Can't trace function calls Jonathan Rajotte-Julien via lttng-dev
2021-03-31 17:55 ` Ramesh Errabolu via lttng-dev
2021-04-02 15:07 ` Jonathan Rajotte-Julien via lttng-dev
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='CAFGSPrw1Ev1c+Ok7tvyzEJOQNDze6fbpzNKFzmH=9hSVYGF69A@mail.gmail.com' \
--to=lttng-dev@lists.lttng.org \
--cc=ramesh.errabolu@gmail.com \
/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 NNTP newsgroup(s).