os.analysis: Fix default thread state when syscall are not traced
authorFrancis Giraldeau <francis.giraldeau@gmail.com>
Wed, 9 Mar 2016 16:44:39 +0000 (11:44 -0500)
committerGenevieve Bastien <gbastien+lttng@versatic.net>
Fri, 11 Mar 2016 15:15:42 +0000 (10:15 -0500)
commit2e3a31c434616ab6c7261a418a324590bf5f549f
tree27e0dcc4713c789e10d49e686c8d298788d2bbda
parentdff70ccd8f00c718528c3f351f5de898520a4e89
os.analysis: Fix default thread state when syscall are not traced

The current behavior is to assign sys_clone to a new thread where the parent's
system call is unknown. When system calls are not traced, the sys_clone exit
event does not occurs, and therefore the thread stays in syscall state, which
is incorrect. In fact, a thread should not enter the system call state when no
syscalls are traced.

For this reason, this patch does not speculate about the state of the
parent, and the child inherit whatever value is set for the parent.

Change-Id: Ic4a3ea8cab7d487a8effe3df282e134292ff8ec1
Signed-off-by: Francis Giraldeau <francis.giraldeau@gmail.com>
Reviewed-on: https://git.eclipse.org/r/68076
Reviewed-by: Hudson CI
Reviewed-by: Genevieve Bastien <gbastien+lttng@versatic.net>
Tested-by: Genevieve Bastien <gbastien+lttng@versatic.net>
Reviewed-by: Matthew Khouzam <matthew.khouzam@ericsson.com>
analysis/org.eclipse.tracecompass.analysis.os.linux.core.tests/src/org/eclipse/tracecompass/analysis/os/linux/core/tests/kernelanalysis/KernelThreadInformationProviderTest.java
analysis/org.eclipse.tracecompass.analysis.os.linux.core/src/org/eclipse/tracecompass/internal/analysis/os/linux/core/kernel/KernelStateProvider.java
analysis/org.eclipse.tracecompass.analysis.os.linux.core/src/org/eclipse/tracecompass/internal/analysis/os/linux/core/kernel/handlers/ProcessForkHandler.java
This page took 0.026296 seconds and 5 git commands to generate.