- 19 Oct, 2018 5 commits
-
-
Tommi Rantala authored
-
Tommi Rantala authored
cppcheck was complaining: [attached_probe.cpp:206]: (warning) %d in format string (no. 1) requires 'int *' but the argument type is 'unsigned int *'. [attached_probe.cpp:206]: (warning) %d in format string (no. 2) requires 'int *' but the argument type is 'unsigned int *'. [attached_probe.cpp:206]: (warning) %d in format string (no. 3) requires 'int *' but the argument type is 'unsigned int *'. While at it, check uname() and sscanf() return values to avoid garbage.
-
Tommi Rantala authored
Valgrind was complaining: ==9103== Warning: invalid file descriptor -1 in syscall close() ==9103== Warning: invalid file descriptor -1 in syscall close()
-
Tommi Rantala authored
-
Brendan Gregg authored
-
- 18 Oct, 2018 3 commits
-
-
Brendan Gregg authored
issue 174 make resolve_kname match exact string
-
Brendan Gregg authored
probe type short names
-
williangaspar authored
-
- 17 Oct, 2018 6 commits
-
-
Brendan Gregg authored
Add file globbing search semantics to list_probes()
-
cneira authored
-
Alastair Robertson authored
-
Alastair Robertson authored
-
cneira authored
-
Brendan Gregg authored
-
- 16 Oct, 2018 14 commits
-
-
Brendan Gregg authored
Support printf("%s") for stack and ustack
-
Peter Sanford authored
This works similarly to how printf'ing a Type::usym works. When verifying the printf format string we treat stack and ustack as Type::string. BPFtrace:get_arg_values now knows how to resolve these. Fixes #10
-
-
Krzesimir Nowak authored
This makes cgroupid function to work fine when building with alpine.
-
Alastair Robertson authored
Allow '.' in idents for golang
-
Alastair Robertson authored
Supports: - LLVM 5 (static build) - LLVM 5 - LLVM 6 - LLVM 7
-
Brendan Gregg authored
ClangParser: Don't exit if kernel headers are not found
-
Peter Sanford authored
When specifying a string literal attach point do not try to expand wildcards if they are present. This specifically is required for Go methods on pointer receivers, which have a '*' in their symbol name.
-
Peter Sanford authored
Allow quoted string attach points so that you can match more than [a-Z0-9]. This specific issue that this fixes is attaching to go functions. These symbols are in the format '<package>.<function>' and can contain unicode letters and digits.
-
Brendan Gregg authored
Implement function cgroupid(path) -> cgroup id
-
Krzesimir Nowak authored
Mention the `cgroup` variable and the `cgroupid` function alongside an example that uses them both.
-
Krzesimir Nowak authored
Currently used image of alpine has a version of musl libc that does not have name_to_handle_at function that is required to resolve the cgroup id. In such case we just use an implementation that says that resolving cgroupid is not supported.
-
Alban Crequy authored
-
Krzesimir Nowak authored
We will wrap the file_handle struct in the next commit. The struct has a flexible array member, which is not supported by C++. Compiler may complain about using it when allocated on stack, even indirectly as a member of a struct. I'm not sure if using this kind of types is even a defined behavior…
-
- 15 Oct, 2018 8 commits
-
-
Brendan Gregg authored
Initial LLVM 7 port
-
Mateusz Lenik authored
Apply Brendan's patch
-
Gaspar authored
* fixes: https://github.com/iovisor/bpftrace/issues/9 * test fix * tests * lifetime * crash fix
-
Brendan Gregg authored
Extend support for char type
-
Brendan Gregg authored
Fix link to count function in reference guide
-
Sandipan Das authored
This fixes the link to the count() function under the Frequency Counting section. Signed-off-by:
Sandipan Das <sandipan@linux.ibm.com>
-
Sandipan Das authored
This extends support for the char type by making the clang parser recognize CXType_Char_U as well. Currently, the clang parser assumes that the char type is always implemented as a signed char. However, for certain architectures like powerpc64, the char type is unsigned and the parser fails to recognize such variables. Signed-off-by:
Sandipan Das <sandipan@linux.ibm.com>
-
Jamie Bainbridge authored
If make is not installed, a clean Fedora install fails with: CMake Error: CMake was unable to find a build program corresponding to "Unix Makefiles". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool. Advise users to install make to resolve this. Signed-off-by:
Jamie Bainbridge <jamie.bainbridge@gmail.com>
-
- 13 Oct, 2018 3 commits
-
-
Alastair Robertson authored
-
Alastair Robertson authored
- KBuildHelper takes kdir, not kpath, as a parameter. - Copy BCC and set has_kpath_source to false when reading kpath from environment variable
-
Brendan Gregg authored
BPFTRACE_KERNEL_SOURCE environment variable
-
- 12 Oct, 2018 1 commit
-
-
cneira authored
-