- 03 Jan, 2019 4 commits
-
-
Brendan Gregg authored
-
Brendan Gregg authored
improve tracepoint not found message
-
Augusto Caringi authored
-
Brendan Gregg authored
-
- 02 Jan, 2019 13 commits
-
-
Brendan Gregg authored
[test] fix runtime-tests cmake settings
-
Matheus Marchini authored
-
Matheus Marchini authored
Co-Authored-By: Birch-san <Birch-san@users.noreply.github.com>
-
Matheus Marchini authored
Co-Authored-By: Birch-san <Birch-san@users.noreply.github.com>
-
Alex Birch authored
-
Alex Birch authored
-
Alex Birch authored
-
Matheus Marchini authored
-
-
Matheus Marchini authored
Assigning the result of str() to a map broke after https://github.com/iovisor/bpftrace/pull/299 landed. This commit fixes it by making sure our call has a type before the final pass of the semantic analyzer. Also moved the default strlen to bpftrace.h to make sure the value is correctly set on unit tests.
-
Brendan Gregg authored
allow isra symbols in kprobe wildcards
-
Brendan Gregg authored
basic positional paramater support
-
Brendan Gregg authored
str() to accept optional length
-
- 01 Jan, 2019 2 commits
-
-
Alex Birch authored
-
Alex Birch authored
-
- 31 Dec, 2018 4 commits
-
-
Brendan Gregg authored
-
Adam Jensen authored
* Add BPFtrace::extract_func_symbols_from_path function * Refactor to add find_wildcard_matches overload that takes an istream * Prepare find_wildcard_matches usage for u(ret)probe types * Add support for wildcard matches with uprobe and uretprobe types * Update add_probes_uprobe_wildcard test * Add test for uprobe wildcard match * Mention uprobe wildcard in readme * Add uprobe support to codegen * Clean up whitespace * Add TODO comment to remove objdump dependency
-
Brendan Gregg authored
Improve build times of codegen tests, fix build-time exhaustion of virtual memory
-
Brendan Gregg authored
Bad zero
-
- 30 Dec, 2018 4 commits
-
-
Brendan Gregg authored
Search PATH for executables when running commands
-
Birch-san authored
-
Daniel Xu authored
This makes it easier for the user to run commands. Specifying abosolute paths to a binary was kind of a pain in the rear.
-
Brendan Gregg authored
-
- 29 Dec, 2018 1 commit
-
-
Alex Birch authored
gather codegen tests into a single compilation unit, for faster build perf (see https://github.com/iovisor/bpftrace/issues/229)
-
- 28 Dec, 2018 4 commits
-
-
Brendan Gregg authored
Better non-root error
-
Brendan Gregg authored
Add -c CMD option
-
Daniel Xu authored
This patch adds a command running option to bpftrace. The user can now run something like: ./bpftrace -e '...' -c 'sleep 5' which is a convenience wrapper around something like: sleep 5 & ./bpfrace -e '...' -p `pidof sleep` `-c` is better because it: * ensures a tighter tracing range around CMD (ie we trace less of the system while it is not running CMD) * makes bpftrace exit (which is convenient) when CMD terminates * previously, it was not possible to get a full trace of CMDs execution and have bpftrace exit upon CMD termination Test Plan: Trivial successful example: ``` $ sudo ./build/src/bpftrace -e 'tracepoint:syscalls:sys_enter_nanosleep { printf("%s nanoslept\n", comm); }' -c '/bin/sleep 1' [sudo] password for dlxu: chdir(/lib/modules/4.19.8-200.fc28.x86_64/build): No such file or directory Attaching 1 probe... sleep nanoslept splunkd nanoslept webrtc_audio_mo nanoslept gnome-terminal- nanoslept webrtc_audio_mo nanoslept gnome-terminal- nanoslept gnome-terminal- nanoslept gnome-terminal- nanoslept gnome-terminal- nanoslept gnome-terminal- nanoslept gnome-terminal- nanoslept gnome-terminal- nanoslept gnome-terminal- nanoslept gnome-terminal- nanoslept gnome-terminal- nanoslept $ ``` Ambigous executable: ``` $ sudo ./build/src/bpftrace -e 'tracepoint:syscalls:sys_enter_nanosleep { printf("%s nanoslept\n", comm); }' -c 'sleep 1' chdir(/lib/modules/4.19.8-200.fc28.x86_64/build): No such file or directory Attaching 1 probe... execve: No such file or directory Failed to spawn child=sleep 1 splunkd nanoslept $ ``` This closes #253
-
williangaspar authored
-
- 27 Dec, 2018 4 commits
-
-
Brendan Gregg authored
Normalize bpftrace(8) man page
-
Daniel Xu authored
This patch normalizes parts of the man page to be in line with the rest.
-
-
Daniel Xu authored
If the user provides a specific PID to trace, it doesn't really make sense to keep running if the tracee terminates. This patch makes bpftrace exit cleanly if the tracee terminates. I spent quite a bit of time thinking about the generic problem of figuring out when an arbitrary pid terminates. After some experiments, here is what I've learned: * wait(2) and waitpid(2) can only wait on child processes (duh) * epoll(2) does not support procfs (or other pseudo filesystems) * inotify does not support procfs either b/c procfs changes are not made through the filesystem (by another userspace entity) * ptrace with PTRACE_SEIZE might work but might have extra overhead on the tracee * the netlink interface for process state changes seems a bit overkill * the only sane solution (AFAICT) is to poll /proc/PID/ for changes Thus, I've made some minor changes to the main event loop to support polling procfs. Test Plan: Make sure non-pid-specific tracing still works: ``` $ sudo ./build/src/bpftrace -e 'uretprobe:/bin/bash:readline { printf("read a line\n"); }' [sudo] password for dlxu: Attaching 1 probe... read a line read a line read a line read a line read a line read a line read a line read a line ^C ``` Verify pid-specific tracing (ie usdt) exits on tracee termination: ``` // in window 1 $ ./python -q // in window 2 $ sudo ~/dev/bpftrace/build/src/bpftrace -p $(pidof python) -e 'usdt:/home/dlxu/dev/cpython/python:function__entry { printf("%s %s\n", str(arg0), str(arg1)) }' [sudo] password for dlxu: Attaching 1 probe... <stdin> <module> // in window 1 >>> print('wow') wow >>> // verify bpftrace has exited in window 2 ```
-
- 26 Dec, 2018 1 commit
-
-
Brendan Gregg authored
[tests] Fix codegen tests for LLVM 5, 6 and 7
-
- 25 Dec, 2018 3 commits
-
-
Brendan Gregg authored
bpftrace adaptations of several iovisor/bcc tcp*.py tools
-
Dale Hamel authored
-
Dale Hamel authored
-