- 02 Jun, 2024 2 commits
- 29 May, 2024 25 commits
-
-
交警大队 authored
-
FJM authored
-
FJM authored
-
oougn authored
-
交警大队 authored
-
交警大队 authored
-
oougn authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
交警大队 authored
-
- 27 May, 2024 13 commits
-
-
oougn authored
-
你宁可空转也不愿被我抢占 authored
-
郑昱笙 authored
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>
-
Daniel Müller authored
Add the -v/--verbose option to control tracing of blazesym internals. Signed-off-by:
Daniel Müller <deso@posteo.net>
-
Daniel Müller authored
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>
-
Daniel Müller authored
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>
-
Daniel Müller authored
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>
-
Daniel Müller authored
Switch the profile example over to using Rust edition 2021 for the latest and greatest. Signed-off-by:
Daniel Müller <deso@posteo.net>
-
Daniel Müller authored
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>
-
Andrii Nakryiko authored
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>
-
mannkafai authored
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>
-
7FrogTW authored
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>
-
7FrogTW authored
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>
-