[valgrind] [Bug 451626] Syscall param bpf(attr->raw_tracepoint.name) points to unaddressable byte(s) in libbpf-tools

2022-03-21 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=451626 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[valgrind] [Bug 451626] Syscall param bpf(attr->raw_tracepoint.name) points to unaddressable byte(s) in libbpf-tools

2022-03-21 Thread Andreas Gerstmayr
https://bugs.kde.org/show_bug.cgi?id=451626 --- Comment #4 from Andreas Gerstmayr --- (In reply to Mark Wielaard from comment #3) > Thanks for doing the research. The fix is simple in that case: > > diff --git a/coregrind/m_syswrap/syswrap-linux.c > b/coregrind/m_syswrap/syswrap-linux.c > index

[valgrind] [Bug 451626] Syscall param bpf(attr->raw_tracepoint.name) points to unaddressable byte(s) in libbpf-tools

2022-03-18 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=451626 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Assignee|jsew...@acm.org

[valgrind] [Bug 451626] Syscall param bpf(attr->raw_tracepoint.name) points to unaddressable byte(s) in libbpf-tools

2022-03-17 Thread Andreas Gerstmayr
https://bugs.kde.org/show_bug.cgi?id=451626 --- Comment #2 from Andreas Gerstmayr --- (In reply to Mark Wielaard from comment #1) > So there are two issues here: > > - WARNING: unhandled eBPF command 35 > This seems to be BPF_LINK_DETACH, which valgrind indeed doesn't handle. Yep, that's

[valgrind] [Bug 451626] Syscall param bpf(attr->raw_tracepoint.name) points to unaddressable byte(s) in libbpf-tools

2022-03-17 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=451626 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark