Skip to content

Commit ff0676e

Browse files
committed
ftrace: Update ftrace event regex
The regex used for the parsing of ftrace events proved inadequate for parsing certain events, namely those that started with opening parentheses, as described in issue #239. The solution is an update to the regex which I have attempted to verify using regex101 in Java mode. Fixes: #239 Signed-off-by: Felix Kuhlmann <felix-kuhlmann@gmx.de>
1 parent 11f36c0 commit ff0676e

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • tracetypes/org.eclipse.tracecompass.incubator.ftrace.core/src/org/eclipse/tracecompass/incubator/internal/ftrace/core/event

tracetypes/org.eclipse.tracecompass.incubator.ftrace.core/src/org/eclipse/tracecompass/incubator/internal/ftrace/core/event/IGenericFtraceConstants.java

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ public interface IGenericFtraceConstants {
6767
* Pattern to match the rest of the event (event name, event fields), like:
6868
* sched_switch: prev_comm=kworker/u16:6 prev_pid=214 prev_prio=120 prev_state=R+ ==> next_comm=swapper/2 next_pid=0 next_prio=120
6969
*/
70-
"(?<name>\\w+)(?<separator>:\\s+|\\(|\\s+->\\s+)(?<data>[^\\)]*)(\\))?" //$NON-NLS-1$
70+
"(?<name>\\w+)(?<separator>:\\s+|\\(|\\s+->\\s+)(?<data>.*)$" //$NON-NLS-1$
7171
);
7272
/**
7373
* comm group in {@link IGenericFtraceConstants#FTRACE_PATTERN}

0 commit comments

Comments
 (0)