Problem Description

Sometimes ptrace not allowed is printed when sage try to attach gdb to it.

Proposed Solution

Suggest user to do something like

echo 0|sudo tee /proc/sys/kernel/yama/ptrace_scope

or can we make the cleaner a parent of the sage process? Then no special privilege is needed.

Alternatives Considered

There is an option of implementing the solution I outlined in https://unix.stackexchange.com/a/787775/296692 to avoid special privilege requirement.

Additional Information

No response

Is there an existing issue for this?

• I have searched the existing issues for a bug report that matches the one I want to file, without success.