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. Start the profiler 8. Execute the JVM task 9. Stop the profiler 10. Stop the JVM Expected output: The profiler will not be able to sample JVM stacks correctly during the first session, but it will do during the second session. Explanati
| 283 | before the first session, but it is started before the second session. |
| 284 | */ |
| 285 | void testFlow3(int argc, char** argv) { |
| 286 | validateArgsCount(argc, 4); |
| 287 | |
| 288 | loadProfiler(); |
| 289 | |
| 290 | loadJvmLib(); |
| 291 | |
| 292 | startProfiler(); |
| 293 | |
| 294 | startJvm(); |
| 295 | |
| 296 | nativeBurnCpu(); |
| 297 | executeJvmTask(); |
| 298 | |
| 299 | stopProfiler(argv[2]); |
| 300 | |
| 301 | startProfiler(); |
| 302 | |
| 303 | nativeBurnCpu(); |
| 304 | executeJvmTask(); |
| 305 | |
| 306 | stopProfiler(argv[3]); |
| 307 | |
| 308 | stopJvm(); |
| 309 | } |
| 310 | |
| 311 | void* jvmThreadWrapper(void* arg) { |
| 312 | loadJvmLib(); |
no test coverage detected