Bug #344
closed--filter ' intfield > intfield2 ' is not supported
100%
Description
Commit used:
============
userspace : (Thu Sep 6 ) a5a9f42 Ensure that read-side functions meet 10-line LGPL criterion
lttng-ust : (Tue Sep 18) 5d3bc5e Fix: get_wait_shm() ust mutex deadlock (add 2 missing exit calls)
lttng-tools:(Tue Sep 18) 4adabd6 Fix: Remove LPOLLNVAL from consumer metadata revents
babeltrace: (Thu Sep 13) f546472 Fix: Documentation cleanup
Scenario:
=========
1)_ Run the instrumented app (in this case, the demo coming with lttng-ust is used)
demo-trace 50 &
2)_ lttng create $SESSION_NAME -o /cluster/temp/sessiondir/$SESSION_NAME
3)_ lttng enable-event ust_tests_demo2:loop -u --filter ' intfield > intfield2 '
get:
libust[24571/24572]: Error: unknown bytecode op 0
(in bytecode_validate_overflow() at lttng-filter-validator.c:184)
libust[24571/24572]: Error: filter bytecode overflow
(in lttng_filter_validate_bytecode() at lttng-filter-validator.c:1103)
Expected Behavior:
==================
Since the tracepoint "ust_tests_demo2:loop" of demo application is instrumented with fields
intfield and intfield2, the user should be able to use them in the filter expression to
compare field vs field .
Files