MCPcopy Create free account
hub / github.com/async-profiler/async-profiler / testFlow2

Function testFlow2

test/test/nonjava/non_java_app.cpp:248–262  ·  view source on GitHub ↗

Here is the flow of the test: 1. Load the profiler 2. Load the JVM library 3. Start the profiler 4. Start the JVM 5. Execute the JVM task 6. Stop the profiler 7. Stop the JVM Expected output: The profiler will not be able to sample JVM stacks correctly. Explanation: The JVM is not yet created when the profiling session starts, so the profiler does not attach to the JVM. */

Source from the content-addressed store, hash-verified

246so the profiler does not attach to the JVM.
247*/
248void testFlow2(int argc, char** argv) {
249 loadProfiler();
250
251 loadJvmLib();
252
253 startProfiler();
254
255 startJvm();
256
257 executeJvmTask();
258
259 stopProfiler(argv[2]);
260
261 stopJvm();
262}
263
264/*
265Here is the flow of the test:

Callers 1

mainFunction · 0.85

Calls 7

loadProfilerFunction · 0.85
loadJvmLibFunction · 0.85
startProfilerFunction · 0.85
startJvmFunction · 0.85
executeJvmTaskFunction · 0.85
stopProfilerFunction · 0.85
stopJvmFunction · 0.85

Tested by

no test coverage detected