DingliZhang/async-profiler
1
0
Fork 0
mirror of https://github.com/async-profiler/async-profiler.git synced 2026-04-29 03:13:34 +00:00
Code Issues Packages Projects Releases 2 Wiki Activity

Add event type details to doc. (#1108)

Browse Source
This commit is contained in:
Kerem Kat
2025-04-06 17:55:00 -07:00
committed by GitHub
parent 94a6f9ca61
commit 2dba71fcf9
3 changed files with 69 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
docs/ProfilingNonJavaApplications.md
View File

@@ -1,11 +1,25 @@
# Profiling Non-Java applications
The scope of profiling non-Java applications is limited to the case when profiler is controlled
programmatically from the process being profiled or with LD_PRELOAD. It is worth noting that
programmatically from the process being profiled or with `LD_PRELOAD`. It is worth noting that
[dynamic attach](IntegratingAsyncProfiler.md#launching-as-an-agent)
which is available for Java is not supported for non-Java profiling.
## C API
## LD_PRELOAD
async-profiler can be injected into a native application through the `LD_PRELOAD` mechanism:
```
LD_PRELOAD=/path/to/libasyncProfiler.so ASPROF_COMMAND=start,event=cpu,file=profile.jfr NativeApp [args]
```
All basic functionality remains the same. Profiler can run in `cpu`, `wall`, `nativemem` and other perf_events
modes. Flame Graph and JFR output formats are supported, although JFR files will obviously lack
Java-specific events.
See [Profiling Modes](ProfilingModes.md) for more examples.
## Controlling async-profiler via the C API
Similar to the
[Java API](IntegratingAsyncProfiler.md#using-java-api),
@@ -83,16 +97,6 @@ int main() {
}
```
In addition, async-profiler can be injected into a native application through LD_PRELOAD mechanism:
```
LD_PRELOAD=/path/to/libasyncProfiler.so ASPROF_COMMAND=start,event=cpu,file=profile.jfr NativeApp [args]
```
All basic functionality remains the same. Profiler can run in `cpu`, `wall` and other perf_events
modes. Flame Graph and JFR output formats are supported, although JFR files will obviously lack
Java-specific events.
## Unstable APIs
These APIs are unstable and might change or be removed in the next version of async-profiler.