From: "Liu, Changcheng via lttng-dev" <lttng-dev@lists.lttng.org>
To: "Christophe Bédard" <bedard.christophe@gmail.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] get function names with lttng-ust-cyg-profile
Date: Fri, 26 Jun 2020 22:22:27 +0800 [thread overview]
Message-ID: <20200626142227.GA12325@jerryopenix> (raw)
Message-ID: <20200626142227.DDJ7pk1mLJKg0SN73GnXN9BUoXEQlbMTuB0H-J5jQ0I@z> (raw)
In-Reply-To: <CAAS9dob7WzAXX+bqca24ELTbAHkMwQvmgmk_r5ci9FVpO4BQYw@mail.gmail.com>
On 10:19 Fri 26 Jun, Christophe Bédard wrote:
> Hi,
> On Tue, 23 Jun 2020 at 21:45, Liu, Changcheng
> <[1]changcheng.liu@intel.com> wrote:
>
> Do you know how to print the call site function_name/offset?
> For example:
> 11 getchar();
> 12
> 13 x = add3(x);
> Currently, it only shows call_site address instead of function name
> with offset.
> func_entry: { cpu_id = 2 }, { ip = 0x55CFA4F5C1EE, debug_info = {
> bin = "instrument+0x11ee", func = "main+0", src = "instrument.c:7"
> }, vpid = 8523 }, { addr = 0x55CFA4F5C1EE, call_site =
> 0x7F27C4B1E0B3 }
> func_entry: { cpu_id = 1 }, { ip = 0x55CFA4F5C1A9, debug_info = {
> bin = "instrument+0x11a9", func = "add3+0", src = "instrument.c:3"
> }, vpid = 8523 }, { addr = 0x55CFA4F5C1A9, call_site =
> 0x55CFA4F5C237 }
> func_exit: { cpu_id = 1 }, { ip = 0x55CFA4F5C1A9, debug_info = { bin
> = "instrument+0x11a9", func = "add3+0", src = "instrument.c:3" },
> vpid = 8523 }, { addr = 0x55CFA4F5C1A9, call_site = 0x55CFA4F5C237 }
> func_exit: { cpu_id = 1 }, { ip = 0x55CFA4F5C1EE, debug_info = { bin
> = "instrument+0x11ee", func = "main+0", src = "instrument.c:7" },
> vpid = 8523 }, { addr = 0x55CFA4F5C1EE, call_site = 0x7F27C4B1E0B3 }
>
> Maybe I'm missing something, but isn't it right here? E.g.
I'm also curious about the output here. "main+0" the function name
"main" is right, but the offset "+0" isn't right.
I've run it for several times, it always shows like the above
output.
So, two questions here:
1. How to show the rigth offset?
2. How to show call_site in "func/offset" format?
>
> debug_info = { bin = "instrument+0x11ee", func = "main+0", src =
> "instrument.c:7" }
>
> Otherwise, I don't think babeltrace can provide any more information.
> Christophe
>
> References
>
> 1. mailto:changcheng.liu@intel.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2020-06-26 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 14:37 get function names with lttng-ust-cyg-profile Liu, Changcheng via lttng-dev
2020-06-23 14:37 ` [lttng-dev] " Liu, Changcheng via lttng-dev
2020-06-23 15:12 ` Matthew Khouzam via lttng-dev
2020-06-23 15:12 ` [lttng-dev] " Matthew Khouzam via lttng-dev
2020-06-23 16:52 ` Christophe Bédard via lttng-dev
2020-06-23 16:52 ` [lttng-dev] " Christophe Bédard via lttng-dev
2020-06-24 1:10 ` Liu, Changcheng via lttng-dev
2020-06-24 1:10 ` [lttng-dev] " Liu, Changcheng via lttng-dev
2020-06-24 1:41 ` Liu, Changcheng via lttng-dev
2020-06-24 1:41 ` [lttng-dev] " Liu, Changcheng via lttng-dev
2020-06-26 14:19 ` Christophe Bédard via lttng-dev
2020-06-26 14:19 ` [lttng-dev] " Christophe Bédard via lttng-dev
2020-06-26 14:22 ` Liu, Changcheng via lttng-dev [this message]
2020-06-26 14:22 ` Liu, Changcheng via lttng-dev
2020-06-27 2:38 ` Liu, Changcheng via lttng-dev
2020-06-27 2:38 ` [lttng-dev] " Liu, Changcheng 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=20200626142227.GA12325@jerryopenix \
--to=lttng-dev@lists.lttng.org \
--cc=bedard.christophe@gmail.com \
--cc=changcheng.liu@intel.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).