From: "changcheng.liu--- via lttng-dev" <lttng-dev@lists.lttng.org> To: lttng-dev@lists.lttng.org Cc: changcheng.liu@aliyun.com Subject: babeltrace convert call_site addr to func/offset Date: Sun, 28 Jun 2020 12:05:02 +0800 [thread overview] Message-ID: <20200628040502.GA36830@jerryopenix> (raw) Hi all, I checked lttng-ust-cry-profile source code: https://github.com/lttng/lttng-ust/blob/master/liblttng-ust-cyg-profile/lttng-ust-cyg-profile.c It traced the runtime virtual-address(VA) of the 1) called function address 2) caller address The value of VA is different from the linked address. Due to ASLR, the VA could be different when running the program every time. The babeltrace could covert the "ip" in the traced context into func/offset. However, there's no context to trace the call_site and babeltrace also support convert the "call_site" into func/offset. Does lttng community has plan to supply the function to support "call_site" context and make babeltrace could convert the "call_site" into func/offset format? B.R. Changcheng
WARNING: multiple messages have this Message-ID (diff)
From: "changcheng.liu--- via lttng-dev" <lttng-dev@lists.lttng.org> To: lttng-dev@lists.lttng.org Cc: changcheng.liu@aliyun.com Subject: [lttng-dev] babeltrace convert call_site addr to func/offset Date: Sun, 28 Jun 2020 12:05:02 +0800 [thread overview] Message-ID: <20200628040502.GA36830@jerryopenix> (raw) Message-ID: <20200628040502.C0jAu2IwKqIYwtgCi3my2aT2JqMGWx_ulmHt2P21Mco@z> (raw) Hi all, I checked lttng-ust-cry-profile source code: https://github.com/lttng/lttng-ust/blob/master/liblttng-ust-cyg-profile/lttng-ust-cyg-profile.c It traced the runtime virtual-address(VA) of the 1) called function address 2) caller address The value of VA is different from the linked address. Due to ASLR, the VA could be different when running the program every time. The babeltrace could covert the "ip" in the traced context into func/offset. However, there's no context to trace the call_site and babeltrace also support convert the "call_site" into func/offset. Does lttng community has plan to supply the function to support "call_site" context and make babeltrace could convert the "call_site" into func/offset format? B.R. Changcheng _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2020-06-28 4:10 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-28 4:05 changcheng.liu--- via lttng-dev [this message] 2020-06-28 4:05 ` [lttng-dev] babeltrace convert call_site addr to func/offset changcheng.liu--- 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=20200628040502.GA36830@jerryopenix \ --to=lttng-dev@lists.lttng.org \ --cc=changcheng.liu@aliyun.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: linkBe 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).