bcc: With latest commits it's imposible to trace more than 200 syscalls.
The root of issue still is in an investigation, but if you have some ideas I would like to know them.
error from libbcc:
mmap: cannot allocate memory
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 26 (5 by maintainers)
Commits related to this issue
- Merge pull request #918 from derek0883/mybcc Handling multiple concurrent probe users. — committed to iovisor/bcc by 4ast 7 years ago
- switch bcc to use single instance per bcc process, instance dir is bcc_pid, fixed issue #940 — committed to derek0883/bcc by deleted user 7 years ago
- Merge pull request #944 from derek0883/mybcc switch bcc to use single instance per bcc process, fixed issue #940 — committed to iovisor/bcc by 4ast 7 years ago
Can we create one instance per BCC process and not per attached function? We could also make this behavior optional - so that scripts that know will need many attaches (like funccount) could opt-out.
If you need to trace all the syscalls, then have you looked at the raw_syscalls:sys_enter, raw_syscalls:sys_exit tracepoints? 2 tracepoints to cover them all. I normally avoid them because I want to trace individual syscalls.