Re: [tracecompass-dev] Question about working with Kernel callstacks

["Petrovic, Denis" <Denis.Petrovic@xxxxxxxxxx>]

Hello,

 

Trace Compass does indeed offer a mechanism for translating addresses to symbol names, and it seems that this is what you’re looking for.

You can find a well-written tutorial with example traces and symbols here [1], and more information here [2].

 

I haven’t got much experience on the subject, so maybe it won’t be that easy in your particular use-case. Fingers crossed :)

 

[1]: https://github.com/tuxology/tracevizlab/blob/e5c5e04050820791f33f9449455a90579040485b/labs/201-lttng-userspace-tracing/README.md#task-3-understanding-the-symbols

[2]: http://archive.eclipse.org/tracecompass/doc/stable/org.eclipse.tracecompass.doc.user/LTTng-UST-Analyses.html

 

Denis.

 

From: tracecompass-dev <tracecompass-dev-bounces@xxxxxxxxxxx> On Behalf Of Evan Galea
Sent: mardi 27 juillet 2021 10:47
To: tracecompass-dev@xxxxxxxxxxx
Subject: [tracecompass-dev] Question about working with Kernel callstacks

 

Hello, and apologies if this is not the correct location to ask the question or if it's been answered before.

 

I am currently tracing the Linux kernel callstack, specifically the 'callstack user' parameter in LTTng's trace events as highlighted. I was wondering if there was a method of converting the values into method names. This may not be something that is specifically done in trace-compass but I was wondering if anyone has had experience with this here.