lttng: Check the state system query results more rigorously
authorAlexandre Montplaisir <alexmonthy@voxpopuli.im>
Mon, 3 Feb 2014 23:20:34 +0000 (18:20 -0500)
committerAlexandre Montplaisir <alexmonthy@voxpopuli.im>
Tue, 4 Feb 2014 20:04:20 +0000 (15:04 -0500)
commit1c471b9ec3eec47830cd1cb81cafd418d15ba0a4
tree9d2838915c5953cfc12122f4918780a28e30c6e5
parent6dd468307826e772f8fb5bedd55f9410b8cf8046
lttng: Check the state system query results more rigorously

Defensive programming dictates we should check for integrity,
correctness, etc. at different layers. And not just once and
assume it's safe at every other levels.

In this case, if we had a trace with a sched_process_free event
arriving first for a new TID, the CFV would assume the Exec_name
attribute would be already set, which was not the case.

Change-Id: I0489937be07282c236978a07e48c4221160bb1d9
Signed-off-by: Alexandre Montplaisir <alexmonthy@voxpopuli.im>
Reviewed-on: https://git.eclipse.org/r/21490
Tested-by: Hudson CI
Reviewed-by: Patrick Tasse <patrick.tasse@gmail.com>
IP-Clean: Patrick Tasse <patrick.tasse@gmail.com>
org.eclipse.linuxtools.lttng2.kernel.ui/src/org/eclipse/linuxtools/internal/lttng2/kernel/ui/views/controlflow/ControlFlowView.java
This page took 0.043864 seconds and 5 git commands to generate.