An error occurred fetching the project authors.
- 16 Jan, 2019 1 commit
-
-
Alexey Ivanov authored
-
- 03 Jan, 2019 1 commit
-
-
Alexey Ivanov authored
* fixed shebangs in tools (and lib) * fixed shebangs in examples * do not mangle shebangs in rpm spec * renamed style-check.sh to c-style-check.sh * factored out python linter to a separate file * added shebang validation to the py-style-check * added shebangs to all python executables
-
- 19 Dec, 2018 1 commit
-
-
Jerome Marchand authored
Many tools rely on the user to type Ctrl-C to end, but don't actually catch the keyboard interrupt and thus show an ugly backtrace when it happens. Let's catch the interrupt.
-
- 26 Sep, 2018 1 commit
-
-
Marko Myllynen authored
Use argparse in cachestat, add --ebpf support. Add --ebpf support for u* tools, finalize language sorting. Remove sole --ebpf string on usage line in tcpsubnet.
-
- 02 Mar, 2018 1 commit
-
-
Teng Qin authored
-
- 02 Apr, 2017 1 commit
-
-
Paul Chaignon authored
-
- 30 Mar, 2017 1 commit
-
-
Paul Chaignon authored
* cc: bcc function to detect the language of a process bcc_procutils_language looks into /proc/$pid/cmdline, /proc/$pid/exe, and /proc/$pid/maps to determine the language. Python wrapper takes a list of candidate languages; if the detected language is not part of the list, None is returned. * u* tools: automatically detect the language Uses the detect_language bcc helper. -l switch can override the detected language. In uthreads and ucalls, the language can be overwritten to 'none' to trace pthreads and syscalls respectively. All tools use the -l switch to set the language, for consistency.
-
- 04 Mar, 2017 1 commit
-
-
Paul Chaignon authored
* Travis CI build to check compliance with PEP8 * argdist: linter cleanup * dbslower: linter cleanup * dbstat: linter cleanup * memleak: linter cleanup * syscount: linter cleanup * tplist: linter cleanup * trace: linter cleanup * ucalls: linter cleanup * uflow: linter cleanup * ugc: linter cleanup * uobjnew: linter cleanup * ustat: linter cleanup
-
- 13 Feb, 2017 1 commit
-
-
Sasha Goldshtein authored
When the target process is missing the required USDT probes, it can be a simple mistake (e.g. attaching a script as Java to a Python process), or a runtime that is not instrumented with the required probes. Attempt to gracefully handle the error and print a helpful message instructing the user why the error might have occurred. ``` $ uthreads -l java $(pidof python) Error attaching USDT probes: the specified pid might not contain the given language's runtime, or the runtime was not built with the required USDT probes. Look for a configure flag similar to --with-dtrace or --enable-dtrace. To check which probes are present in the process, use the tplist tool. ```
-
- 08 Feb, 2017 1 commit
-
-
Sasha Goldshtein authored
Filter out collections that are shorter than x milliseconds by using `ugc -M x`. Display only collections that contain a certain string s in their description by using `ugc -F s`. The latter option is not implemented in the kernel, but rather just before printing the event in the user script (for simplicity), and documented as such.
-
- 19 Dec, 2016 5 commits
-
-
Sasha Goldshtein authored
-
Sasha Goldshtein authored
-
Sasha Goldshtein authored
Add Node support for gc__start and gc__done probes, which includes GC type flag parsing.
-
Sasha Goldshtein authored
For runtimes that make it available, we now extract GC event information such as heap sizes and print this information in addition to the GC duration and timestamp.
-
Sasha Goldshtein authored
`ugc` monitors GC start and end events in Java, Python, and Ruby, printing out a message when a GC cycle completes along with the duration of the GC and an optional additional description that depends on the target language. NOTE: This WIP does not have any interesting additional descriptions yet. Usage example: ``` ugc java 1448 # monitor Java GCs in process 1448 ```
-