From: "Christophe Bédard via lttng-dev" <lttng-dev@lists.lttng.org> To: "Liu, Changcheng" <changcheng.liu@intel.com> Cc: lttng-dev <lttng-dev@lists.lttng.org> Subject: Re: get function names with lttng-ust-cyg-profile Date: Fri, 26 Jun 2020 10:19:38 -0400 [thread overview] Message-ID: <CAAS9dob7WzAXX+bqca24ELTbAHkMwQvmgmk_r5ci9FVpO4BQYw@mail.gmail.com> (raw) In-Reply-To: <20200624014141.GA4166707@jerryopenix> [-- Attachment #1.1: Type: text/plain, Size: 1412 bytes --] Hi, On Tue, 23 Jun 2020 at 21:45, Liu, Changcheng <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. debug_info = { bin = "instrument+0x11ee", func = "main+0", src = > "instrument.c:7" } > Otherwise, I don't think babeltrace can provide any more information. Christophe [-- Attachment #1.2: Type: text/html, Size: 2163 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
WARNING: multiple messages have this Message-ID (diff)
From: "Christophe Bédard via lttng-dev" <lttng-dev@lists.lttng.org> To: "Liu, Changcheng" <changcheng.liu@intel.com> Cc: lttng-dev <lttng-dev@lists.lttng.org> Subject: Re: [lttng-dev] get function names with lttng-ust-cyg-profile Date: Fri, 26 Jun 2020 10:19:38 -0400 [thread overview] Message-ID: <CAAS9dob7WzAXX+bqca24ELTbAHkMwQvmgmk_r5ci9FVpO4BQYw@mail.gmail.com> (raw) Message-ID: <20200626141938.Mx6oiMncRdEmhqJgzPMwl-1hYmUpv5l39cqiX2-2HGg@z> (raw) In-Reply-To: <20200624014141.GA4166707@jerryopenix> [-- Attachment #1.1: Type: text/plain, Size: 1412 bytes --] Hi, On Tue, 23 Jun 2020 at 21:45, Liu, Changcheng <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. debug_info = { bin = "instrument+0x11ee", func = "main+0", src = > "instrument.c:7" } > Otherwise, I don't think babeltrace can provide any more information. Christophe [-- Attachment #1.2: Type: text/html, Size: 2163 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 prev parent reply other threads:[~2020-06-26 14:20 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 [this message] 2020-06-26 14:19 ` Christophe Bédard via lttng-dev 2020-06-26 14:22 ` Liu, Changcheng via lttng-dev 2020-06-26 14:22 ` [lttng-dev] " 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=CAAS9dob7WzAXX+bqca24ELTbAHkMwQvmgmk_r5ci9FVpO4BQYw@mail.gmail.com \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.