python3Packages.libdebug: init at 0.9.0

[MrSmoer]

Libdebug is "A Python library to debug binary executables, your own way."

It is easlily scriptable, common in the CTF-community and also very handy for crude binary-patching.
The README has a great overview:
https://github.com/libdebug/libdebug

I had to replace the pythonImportsCheckPhase, which is really not optimal, because during import it tries to create a history-log in $HOME/libdebug/.cache directory, which fails at /homeless-shelter.
I could probably provide a patch to disable this feature during building (which doesn't sound like the way patches should work); I am not really sure about that.

This is my first time opening a PR in nixpkgs, so I added myself to the maintainers-list.nix.
I am not full sure on what exactly to do with the todo list down there, so any help with that would be appreciated.

Things done

• Built on platform:
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• Tested, as applicable:
  • NixOS tests in nixos/tests.
  • Package tests at passthru.tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.
• Ran nixpkgs-review on this PR. See nixpkgs-review usage.
• Tested basic functionality of all binary files, usually in ./result/bin/.
• Nixpkgs Release Notes
  • Package update: when the change is major or breaking.
• NixOS Release Notes
  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

---

Add a 👍 reaction to pull requests you find important.

[Sigmanificient]

Can you also try to run the test suite?

• https://github.com/libdebug/libdebug/blob/main/test/run_suite.py

[MrSmoer]

I did a few weeks ago, back then a few test seemed fundamentally broken to me, but that was probably my fault; I will try again

[MrSmoer]

Unrelated to the issues i ran into before - outside of the nix-build environment - it tries to debug a few executeables as part of the tests and seems to be unable to open /proc/1129/maps, failing with No such file or directory.
I am not sure why this fails; whether it is because of sandboxing (probably) and whether one would like to give those privileges to build-process anyways.
I am honestly not sure on how to continue with that from this point, what do you think? @Sigmanificient

The tests will also fail in general when the builder has /proc/sys/kernel/yama/ptrace_scope set to 2 - admin-only attach or 3 - no attach