Function testFlow4

test/test/nonjava/non_java_app.cpp:337–352

Here is the flow of the test: 1. Load the profiler 2. Load the JVM library 3. Start the JVM on a different thread 4. Start the profiler 5. Execute the JVM task 6. Stop the profiler 7. Stop the JVM Expected output: The profiler should be able to profile the JVM task. Explanation: The same as flow 1, except that profiler will have to attach the caller thread to the JVM. */

The same as flow 1, except that profiler will have to attach the caller thread to the JVM.
*/
void testFlow4(int argc, char** argv) {
    struct timespec wait_time = {(time_t)(2), 0L};

    loadProfiler();

    pthread_t thread;
    pthread_create(&thread, NULL, jvmThreadWrapper, NULL);

    nanosleep(&wait_time, NULL);

    startProfiler();

    nanosleep(&wait_time, NULL);

    stopProfiler(argv[2]);
}

int main(int argc, char** argv) {
    validateArgsCount(argc, 3);