From 55e90f33b0503c68ef5e6e198c70db4d1ace4519 Mon Sep 17 00:00:00 2001 From: Philippe Proulx Date: Thu, 27 Oct 2016 14:06:31 -0400 Subject: [PATCH] addr2line: link to man page Signed-off-by: Philippe Proulx --- 2.7/lttng-docs-2.7.txt | 6 ++---- 2.8/lttng-docs-2.8.txt | 6 ++---- 2 files changed, 4 insertions(+), 8 deletions(-) diff --git a/2.7/lttng-docs-2.7.txt b/2.7/lttng-docs-2.7.txt index e3cdd17..bb6718b 100644 --- a/2.7/lttng-docs-2.7.txt +++ b/2.7/lttng-docs-2.7.txt @@ -4239,10 +4239,8 @@ Assuming no event record is lost, having only the function addresses on entry is enough to create a call graph, since an event record always contains the ID of the CPU that generated it. + -You can use a tool like -https://sourceware.org/binutils/docs/binutils/addr2line.html[cmd:addr2line] -to convert function addresses back to source file names and -line numbers. +You can use a tool like man:addr2line(1) to convert function addresses +back to source file names and line numbers. * **path:{liblttng-ust-cyg-profile.so}** is a more robust variant which also works in use cases where event records might get discarded or diff --git a/2.8/lttng-docs-2.8.txt b/2.8/lttng-docs-2.8.txt index e72fc38..ed0c9c6 100644 --- a/2.8/lttng-docs-2.8.txt +++ b/2.8/lttng-docs-2.8.txt @@ -4302,10 +4302,8 @@ Assuming no event record is lost, having only the function addresses on entry is enough to create a call graph, since an event record always contains the ID of the CPU that generated it. + -You can use a tool like -https://sourceware.org/binutils/docs/binutils/addr2line.html[cmd:addr2line] -to convert function addresses back to source file names and -line numbers. +You can use a tool like man:addr2line(1) to convert function addresses +back to source file names and line numbers. * **path:{liblttng-ust-cyg-profile.so}** is a more robust variant which also works in use cases where event records might get discarded or -- 2.34.1