On 10/28/13 1:23 PM, Masami Hiramatsu wrote:
By the way, what happens if multiple binaries has same SDT marker?
Yeah, perf list shows just one and ignores others. However, if we
probe one, and run binary which use the other one, user will never
see the marker.
So, it still needs a concrete binary path to list or, we should
support a syntax which specify actual binary, as like as below.
perf probe 'my_event=%libc:setjmp@/lib64/libc.so.6'
And perf list may show the marker as in same syntax (for copy&paste).
# perf list --sdt
%libc:setjmp@/lib64/libc.so.6
...
Note that we need '%' to separate namespace :(, since user can define
any marker(provider) name in their binary...
Sure, you need to support that sort of 'fully qualified name' for
duplicate symbols but the default 'libc:setjmp' should still point
to system libc.
This is an example where tracing libc that's relevant to most of
the users should take priority over the 'duplicate marker in
obscure executable' corner case case.
Pekka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
