Closed vigbalu closed 3 years ago
The intention was, that the plugin should detect continuation of execution (or respectively the stop of execution) and invalidate the cached state of the thread. While the execution is stopped, it should be save to cache the current task.
i couldn't find any gdb api or decent place in plugin code to invalidate the cache state. Possible places are before/after the "ompd" commands and start/end of function call "ompd_tool_test".
can i proceed with above ?
Sure, we can fix this later once we find a way to detect that execution continues.
With OMPT-plugin, when comparing ompt and ompd data, ompd_thread handle saves current task in a variable and reuses for successive calls. When "omp task" is used, each thread might use different task at different instances. This patch retrieve current task through ompd api everytime it gets called. These will fix the test cases failed due to #41.