Project

General

Profile

Actions
Copy link

Bug #342

closed

Error reported when the instrumented applications starts (related to filter)

Added by Tan le tran about 12 years ago. Updated about 12 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Christian Babeux
Target version:
LTTng - 2.1 stable
Start date:
09/18/2012
Due date:
% Done:

0%

Estimated time:

Description

Scenario: =========
0)_ No instrumented applications running.
1)_ lttng create ses1 -o /cluster/temp/sessiondir/ses1
2)_ enable an event with an invalid filter:
lttng enable-event ust_tests_demo2:loop -u --filter ' "myString" "yourString" '

3)_ Run the instrumented application (ex:demo) that has the above tracepoint.
demo-trace

4)_ The following error is received:
libust[24336/24337]: Error: Filter reloc offset 24 is not within data
(in handle_message() at lttng-ust-comm.c:299)
libust[24336/24337]: Error: Error handling message for global socket (in ust_listener_thread() at lttng-ust-comm.c:867)
libust[24336/24337]: Error: incorrect message size (global socket): 24
(in ust_listener_thread() at lttng-ust-comm.c:878)
libust[24336/24336]: Error: Timed out waiting for ltt-sessiond (in lttng_ust_init() at lttng-ust-comm.c:1030)

Expected Behavior:
================
Can the error printout be suppressed as this type of error is confusing for
the application.

Files

log.txt (22.1 KB) log.txt Terminal log with "sessiond -vvv" Tan le tran, 09/18/2012 05:02 PM
Actions
Copy link
 #1

Updated by Tan le tran about 12 years ago

The above issue has been observed with the following commits:

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

Actions
Copy link
 #2

Updated by Mathieu Desnoyers about 12 years ago

  • Project changed from LTTng-UST to LTTng-tools

This looks like with this filter info, the tools provide a corrupted filter to the app. This is why lttng-ust complain with ERR. The complain should not show up, but this should be fixed by investigating why lttng-tools send the corrupted filter info from this invalid filter.

Actions
Copy link
 #3

Updated by David Goulet about 12 years ago

  • Target version set to 2.1 stable
Actions
Copy link
 #4

Updated by David Goulet about 12 years ago

  • Status changed from New to Confirmed
  • Assignee set to Christian Babeux
Actions
Copy link
 #5

Updated by Christian Babeux about 12 years ago

  • Status changed from Confirmed to Feedback

Hi Tan,

I was not able to reproduce this issue. Are you able to reproduce it with the latest HEAD of lttng-tools/lttng-ust?

Actions
Copy link
 #6

Updated by Tan le tran about 12 years ago

Hi Christian,

It is still there with the latest HEAD (from yesterday):

userspace : (sep6) a5a9f42 Ensure that read-side functions meet 10-line LGPL criterion
lttng-ust : (sep26) 38f5f44 Fix: manpage typo "-lllttng-ust" -> "-llttng-ust"
lttng-tools: (sep26) 529f6ac Update version to v2.1.0-rc4
babeltrace : (sep20) 9b3c1d6 Fix: emf uri: surround by " "

Short log from today (sep28): =============================
SC-1:/home/test_apps # lttng list u
UST events:
------------
None

SC-1:/home/test_apps #
SC-1:/home/test_apps # lttng list
Currently no available tracing session
SC-1:/home/test_apps #
SC-1:/home/test_apps # lttng create ses1
Session ses1 created.
Traces will be written in /root/lttng-traces/ses1-20120928-092628
SC-1:/home/test_apps # lttng enable-event ust_tests_demo2:loop -u --filter ' "myString" "yourString" '
UST event ust_tests_demo2:loop created in channel channel0
Filter ' "myString" "yourString" ' successfully set
SC-1:/home/test_apps #
SC-1:/home/test_apps # more demo-trace
#!/bin/sh

LD_PRELOAD=/home/test_apps/liblttng-ust-provider-ust-tests-demo.so:/home/test_apps/liblttng-ust-provider-ust-tests-demo3.so /home/test_apps/demo
SC-1:/home/test_apps #
SC-1:/home/test_apps # ./demo-trace
libust[29351/29352]: Error: Filter reloc offset 24 is not within data
(in handle_message() at lttng-ust-comm.c:299)
libust[29351/29352]: Error: Error handling message for global socket (in ust_listener_thread() at lttng-ust-comm.c:867)
libust[29351/29352]: Error: incorrect message size (global socket): 24
(in ust_listener_thread() at lttng-ust-comm.c:878)
libust[29351/29351]: Error: Timed out waiting for ltt-sessiond (in lttng_ust_init() at lttng-ust-comm.c:1030)
Demo program starting.
Tracing... done.

SC-1:/home/test_apps # lttng -h
LTTng Trace Control 2.1.0-rc4 - Basse Messe

Regards,
Tan

Actions
Copy link
 #7

Updated by Christian Babeux about 12 years ago

  • Status changed from Feedback to Resolved

Hi Tan,

I was able to reproduce this issue. I was missing the "==" in the filter because for some reason Redmine interpret these characters as whitespace.

This issue is fixed in lttng-ust changeset 885b1dfd5d050ed5610721d9ec840bfd121644ec.

Thank you for reporting.

Actions
Copy link

Also available in: Atom PDF