Hi,
As part of a big software safety certification effort, we are looking into
making sure that some functions of our API do not allocate memory and do
not use any blocking syscalls.
This part is done and is working (using kmem_mm_page_{alloc,free} for
memory allocations for now). However, if we
On Tue, 12 May 2020 at 08:27, Mathieu Desnoyers <
mathieu.desnoy...@efficios.com> wrote:
> How does your test program issue the system call ? Is it directly with
> syscall() (see syscall(2) man page), or
> does it call into libc ? Is your entire libc compiled with
> -fno-omit-frame-pointer ?
>
In
On Wed, 13 May 2020 at 10:18, Genevieve Bastien via lttng-dev <
lttng-dev@lists.lttng.org> wrote:
> We had a very very experimental branch with it, using backtrace first,
> then unwind. But it is not suggested, not performant. It's far from the
> correct desired implementation, for which Mathieu c
Hi,
Babeltrace is doing exactly what it should as far as I know.
>
yes, but babeltrace *can* provide the information if:
* ip and vpid contexts are enabled (for userspace), e.g.
$ lttng add-context --userspace --type=ip --type=vpid
* LTTng state dump events are enabled, e.g.
$ lttng enable-ev
Hi,
On Tue, 23 Jun 2020 at 21:45, Liu, Changcheng
wrote:
> Do you know how to print the call site function_name/offset?
> For example:
> 11 getchar();
> 12
> 13 x = add3(x);
> Currently, it only shows call_site address instead of function name with
> o
Hi,
You have to register for an account first (top right corner):
https://bugs.lttng.org/account/register
Once your account is created and you've logged in, you can open a new
issue by clicking on "new issue" (or using this link:
https://bugs.lttng.org/projects/urcu/issues/new)
Christophe
On T
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
