https://bugzilla.suse.com/show_bug.cgi?id=1221763 https://bugzilla.suse.com/show_bug.cgi?id=1221763#c4 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |giuliano.belinassi@suse.com Flags| |needinfo?(giuliano.belinass | |i@suse.com) --- Comment #4 from Jiri Slaby <jslaby@suse.com> --- (In reply to Giuliano Belinassi from comment #0)
Recent updates of tumbleweed broke `ptrace(PTRACE_ATTACH, ...)` when attaching to a process from the same user. This breaks attaching a debugger (gdb) to a process and userspace livepatching. A single line reproducer in a clean system is:
``` $ sleep 5000 & gdb -p $(pidof sleep) ```
If you see the following message:
``` Attaching to process 12606 ptrace: Operation not permitted. ``` This means ptrace is not working. As a contrast, running gdb with sudo works as intended.
Value of /proc/sys/kernel/yama/ptrace_scope: ``` $ cat /proc/sys/kernel/yama/ptrace_scope 1 ```
So this actually works as expected and was supposed to work like this forever. Could you clarify what "Recent updates of tumbleweed" broke this? -- You are receiving this mail because: You are on the CC list for the bug.