Skip to content

Changes

Summary

  1. Fix FTrace Text in the case of Docker/K8S traces (details)
Commit ffbbc088c53bed20c32d162fcf62152de17f4dd3 by Matthew Khouzam
Fix FTrace Text in the case of Docker/K8S traces

Docker containers have exec names like "comm=runc:[2:INIT]",
the regular expressions need to be updated to accommodate this.

1- the separator type (=:) needs to be retained and
consistent on a per-event basis
2- the fields need to be parsed in a more aggressive way,
allowing consumption of the elems
3- Brackets are acceptable for comms even though they are also arrays

This lead to an "excemption" for the patterns  command:[level:phase]
from the value parser.

Signed-off-by: Matthew Khouzam <matthew.khouzam@ericsson.com>
Change-Id: I19d54073ab5ac6fd9b93fdc0e6a48c1d35e6913c
Reviewed-on: https://git.eclipse.org/r/c/tracecompass.incubator/org.eclipse.tracecompass.incubator/+/200223
Tested-by: Patrick Tasse <patrick.tasse@gmail.com>
Tested-by: Trace Compass Bot <tracecompass-bot@eclipse.org>
Reviewed-by: Patrick Tasse <patrick.tasse@gmail.com>
The file was modified tracetypes/org.eclipse.tracecompass.incubator.ftrace.core.tests/src/org/eclipse/tracecompass/incubator/ftrace/core/tests/event/FtraceFieldTest.java (diff)
The file was modified tracetypes/org.eclipse.tracecompass.incubator.ftrace.core/src/org/eclipse/tracecompass/incubator/internal/ftrace/core/event/GenericFtraceField.java (diff)