Hello!
Currently, callstack collection in LTTng is only available for kernel-space
events with context fields *callstack-kernel *and *callstack-user*.
Is it expected that callstack collection for LTTng-UST will be added too?
And if it is expected, then how soon?
Best regards,
Valentin Grigorev
_
Yeah, as far as I know, perf [1] is successfully using libunwind to provide
callstacks. Probably, LTTng team should think about it too, if there are no
serious obstacles.
[1]: https://perf.wiki.kernel.org/index.php/Main_Page
Best regards,
Valentin Grigorev
On Thu, Mar 26, 2020 at 11:53 PM Mili
Hmm, I don't know unfortunately, it should be checked
Best regards,
Valentin Grigorev
On Fri, Mar 27, 2020 at 4:55 PM Mathieu Desnoyers <
mathieu.desnoy...@efficios.com> wrote:
> Last time I checked, the main issue with perf's handling of cases that
> lack frame pointers
> is that they grab a ~
Hello!
Currently, I'm developing a process monitor on the base of LTTng, and I
face the challenge of accessing command-line arguments passed to execve
syscall.
I'm using LTTng live session and Babeltrace 2 C API to analyze events in
online mode.
syscall_entry_execve event has 3 payload fields: fi
Thanks for the information, Mathieu
Best regard,
> Valentin Grigorev
___
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
Hello!
I'm using LTTng live session and Babeltrace 2 C API to analyze events in
online mode.
I would like to route event processing statically (using IDs, without
parsing strings). And currently, I don't understand if it is possible with
LTTng.
Babeltrace 2 C API provides bt_event_class_get_id f
Hello!
Is it planned to publish LTTng 2.12 packages for Linux distributives except
Ubuntu and Debian. Packages for RedHat / CentOS, Fedora, Arch, etc are
available for previous versions.
Best regards,
Valentin Grigorev
___
lttng-dev mailing list
lttng-d
