Matthias Bertschy

Here is what I see: ``` [root@localhost matthias]# ls -1d /sys/kernel/debug/tracing/events/syscalls/sys_*_execve /sys/kernel/debug/tracing/events/syscalls/sys_enter_execve /sys/kernel/debug/tracing/events/syscalls/sys_exit_execve ``` So `trace open` and `trace mount` have the same issue: ``` [matthias@localhost ~]$ sudo ig trace...

> The `trace signal` gadgets only use **exit** tracepoints if it is called with `ig trace signal --kill-only`. > > It seems consistent: only **exit** tracepoints fail. But I don't...

I have suggested a workaround to our customer in the meantime: https://github.com/kubescape/kubescape/issues/1596#issuecomment-1948428179

Let's revisit it from time to time to check resolution...

I think with goreleaser we can build rpm, deb, etc... would it help if we provide these as release artifacts?

We no longer build with CGO_ENABLED so we don't care about the GLIBC, do we?

Do you know how I can test that? I mean without spinning up 5 different VMs?

The latest release is built without cgo. Can we try now? On Wed, Feb 21, 2024, 13:37 Hollow Man ***@***.***> wrote: > Do you know how I can test that?...

@agarcia-oss can you help us giving your thoughts on David's questions?

@ioannisgk can you post here your kernel version from `uname -a` or equivalent?