It'd be good to state publicly the oldest kernel and glibc (or even other libc versions) we support.
This would allow us to remove some legacy code or force support for legacy code.

This shouldn't require test to be functional (e.g. for some cases like module drivers it could be hard),
but LTP to be compiled and when difficult/impossible to achieve this functionality, it could resulted in TCO

The PRoot documentation states:

Also, developers can use PRoot as a generic Linux process instrumentation engine thanks to its extension mechanism, see CARE_ for an example.

But CARE is a pretty big meaty example with a lot of its own logic in addition to the syscall stuff it uses PRoot to manage. I was wondering if you could bundle a minimal example that just shows how to build a minimal prog

Make the number of ELF section headers being tracked dynamic, or just add a comment about the array size being dynamic.
Elf64_Shdr headers[0x10];
"magic number - pls, comment on why it's 0x10"

Document in Readme.md what each dependancy is used for.
"perl -- for checking code style errors (or something similar)"

Fix man page installation
See debian/libsyscall-intercept.dev.manpages

One problem with faulting programs under KRF is that KRF might decide to inject a fault during the dynamic link/load phase, aborting ld-linux.so instead of the actual target image. This usually isn't helpful, since it doesn't indicate any mistakes in the target itself.

It should be possible to check the loaded program's name via the current task, probably via comm. We should use that (or

Nitro is currently lacking in documentation, this should be improved. I am creating this issue to track the progress of documentation project.

As of what the documentation should contain, as a starting point, I think we should have:

• Basic API Documentation: Basic documentation of classes and functions.
• Higher-Level Description of Project Structure: What are the different