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. */
| 246 | so the profiler does not attach to the JVM. |
| 247 | */ |
| 248 | void 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 | /* |
| 265 | Here is the flow of the test: |
no test coverage detected