For more involved user space tracing I highly recommend
https://github.com/wolfpld/tracy
It is a different approach and probably already has all the bells and
whistles you require.
Hi Mathieu,
On 2024-12-11 10:43, Mathieu Desnoyers via lttng-dev wrote:
> Another approach then is to add tracepoints within your C++ standard
> library functions. Then you can use the caller ip of _those_ functions
> and pass them to the tracepoint as "ip" context override.
That's difficult, as
On 2024-12-11 05:32, Alexander Krabler via lttng-dev wrote:
Hi Christophe and Kienan,
Internal
On 12/2/24 4:17 PM, Christophe Bédard via lttng-dev wrote:
I did the same thing a while ago, i.e., trigger tracepoints on
malloc/free/etc. using liblttng-ust-libc-wrapper and collect userspace
callst
Hi Christophe and Kienan,
Internal
On 12/2/24 4:17 PM, Christophe Bédard via lttng-dev wrote:
> I did the same thing a while ago, i.e., trigger tracepoints on
> malloc/free/etc. using liblttng-ust-libc-wrapper and collect userspace
> callstack information (so that the indirect calls to malloc/fre
Hi Alexander, Christophe,
On 12/2/24 4:17 PM, Christophe Bédard via lttng-dev wrote:
> Hi,
>
> I did the same thing a while ago, i.e., trigger tracepoints on
> malloc/free/etc. using liblttng-ust-libc-wrapper and collect userspace
> callstack information (so that the indirect calls to malloc/free
Hi,
I did the same thing a while ago, i.e., trigger tracepoints on
malloc/free/etc. using liblttng-ust-libc-wrapper and collect userspace
callstack information (so that the indirect calls to malloc/free can be
removed from an application).
There is a userspace callstack context implementation her
Hello,
we want to record stacktraces at specific userspace events like e.g. calls to
malloc and free using liblttng-ust-libc-wrapper.so.
There is the callstack-user context to achieve this in general, however, it
seems like tracing of userspace stacktraces is only available in the kernel
tracin
