lttng-dev Archive on lore.kernel.org
 help / color / Atom feed
* babeltrace convert call_site addr to func/offset
@ 2020-06-28  4:05 changcheng.liu--- via lttng-dev
  2020-06-28  4:05 ` [lttng-dev] " changcheng.liu--- via lttng-dev
  0 siblings, 1 reply; 2+ messages in thread
From: changcheng.liu--- via lttng-dev @ 2020-06-28  4:05 UTC (permalink / raw)
  To: lttng-dev; +Cc: changcheng.liu

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [lttng-dev] babeltrace convert call_site addr to func/offset
  2020-06-28  4:05 babeltrace convert call_site addr to func/offset changcheng.liu--- via lttng-dev
@ 2020-06-28  4:05 ` changcheng.liu--- via lttng-dev
  0 siblings, 0 replies; 2+ messages in thread
From: changcheng.liu--- via lttng-dev @ 2020-06-28  4:05 UTC (permalink / raw)
  To: lttng-dev; +Cc: changcheng.liu

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-28  4:05 babeltrace convert call_site addr to func/offset changcheng.liu--- via lttng-dev
2020-06-28  4:05 ` [lttng-dev] " changcheng.liu--- via lttng-dev

lttng-dev Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/lttng-dev/0 lttng-dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lttng-dev lttng-dev/ https://lore.kernel.org/lttng-dev \
		lttng-dev@lists.lttng.org
	public-inbox-index lttng-dev

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.lttng.lists.lttng-dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git