The code changes in this commit improve the functionality
of the uprobe by using the function name instead of the
function offset. This change is made to simplify the code
and make it more readable.

Signed-off-by: yunwei37 <1067852565@qq.com>

Add the -v/--verbose option to control tracing of blazesym internals.

Signed-off-by: Daniel Müller <deso@posteo.net>

Update the blazesym submodule to version 0.2.0-alpha.5. Also change the
dependency to using the default features, which includes DWARF support
and transparent symbol demangling.
The profile example is overhauled to use the changed APIs and improve
the code to be less redundant.

Signed-off-by: Daniel Müller <deso@posteo.net>

It is entirely possible for symbolization to fail for legitimate reasons
when profiling the system continuously. For example, a process could
terminate between the time addresses from it were captured and we
attempt to symbolize them, in which case an error will be reported by
blazesym.
As it stands such an error will shoot down the profiler, which is not
the desired behavior. With this change we handle such errors more
gracefully by just printing an error message.

Signed-off-by: Daniel Müller <deso@posteo.net>

Update the clap dependency as used by the profile example to version
4.0, in order to not fall behind upstream too much.

Signed-off-by: Daniel Müller <deso@posteo.net>

Switch the profile example over to using Rust edition 2021 for the
latest and greatest.

Signed-off-by: Daniel Müller <deso@posteo.net>

When building the Rust examples we see a warning:

  > warning: some crates are on edition 2021 which defaults to
  >          `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
  > note: to keep the current resolver, specify `workspace.resolver = "1"`
  >       in the workspace root's manifest
  > note: to use the edition 2021 resolver, specify `workspace.resolver = "2"`
  >       in the workspace root's manifest

Fix it by switching to resolver 2.

Signed-off-by: Daniel Müller <deso@posteo.net>

LLVM/Clang 18 is available now, run against it as well. This also should
fix current LLVM 17 failure, which assumes LLVM 17 is the latest one.

Signed-off-by: Andrii Nakryiko <andrii@kernel.org>

When CARGO exists external project blazesym will build, It not works
with --features=cheader option. profile depends on blazesym,
correct blazesym include directories.

Signed-off-by: mannkafai <mannkafai@users.noreply.github.com>

Add `-i <interface>` option for user to specify which network
interface they want to watch for, if not specified, `lo` is used.

Signed-off-by: Jacky Yin <jjyyg1123@gmail.com>

When we have multiple calls to `inet_ntoa()`, this function
might return the same char* even though the underlying string has been
modified.

We'll get the same string if we use this function in a row in a single printf
function(because char* pointed to the same location).

Signed-off-by: Jacky Yin <jjyyg1123@gmail.com>

Update the blazesym submodule to the most recent snapshot.

Signed-off-by: Daniel Müller <deso@posteo.net>

Add 11, 12, and 13 versions, to make sure examples works on all of them.

Signed-off-by: Andrii Nakryiko <andrii@kernel.org>

Add the note about needing at least Clang v11 to successfully compile examples.

Signed-off-by: Andrii Nakryiko <andrii@kernel.org>

In namespaced environments like containers or WSL2 the `minimal` example
would not work, because of namespace pid and real PID of userspace
process not necessarily matching. Add `minimal_ns` example to show how
to handle PID translation in namespaced environments.

Signed-off-by: Hosein Bakhtiari <h.bakhtiary.z@gmail.com>

Add support for clang-format so the code style would be consistent
throughout the whole project for C examples.

Signed-off-by: Hosein Bakhtiari <h.bakhtiary.z@gmail.com>

Running example/c/profile on a virtual machine results in
libbpf_num_possible_cpus calculating the wrong number of CPUs, causing the
program to fail to set up performance monitor on a CPU/Core and throw an
error. In contrast, the Rust implementation ignores this error and continues
to execute.

This fix only applies to the C implementation.

Signed-off-by: ZhengSong Tu <tzssangglass@gmail.com>

Signed-off-by: Abhishek Dubey <adubey@linux.ibm.com>

Signed-off-by: Abhishek Dubey <adubey@linux.ibm.com>

Add an example to trace `kill` and `tgkill` syscalls using libbpf's
`SEC(ksyscall)` program type.

Signed-off-by: syogaraj <yoga30696@gmail.com>

Rather than relying on the system's llvm-strip tool, which could be missing
and failing the build, use "bpftool" to generate bpf object files.

Signed-off-by: Rutvik Patel <heyrutvik@gmail.com>