LTTng bugs repository: Issueshttps://bugs.lttng.org/https://bugs.lttng.org/themes/lttng/favicon/a.ico?14249722912020-02-17T23:46:06ZLTTng bugs repository
Redmine LTTng-UST - Bug #1238 (Resolved): AddressSanitizer detects an global buffer overflow when we iter...https://bugs.lttng.org/issues/12382020-02-17T23:46:06ZMathieu Desnoyersmathieu.desnoyers@efficios.com
<p>Building lttng-ust with:</p>
<p>CC="clang-9" CFLAGS="-g -O0 -fsanitize=address" LDFLAGS="-fsanitize=address -fno-omit-frame-pointer" ./configure && make</p>
<p>then running tests/hello/hello :</p>
<p>=================================================================<br />5772ERROR: AddressSanitizer: global-buffer-overflow on address 0x7f1e9d589270 at pc 0x7f1e9d16103f bp 0x7fff2e875ff0 sp 0x7fff2e875fe8<br />READ of size 4 at 0x7f1e9d589270 thread T0<br /> #0 0x7f1e9d16103e in hashlittle /home/efficios/git/lttng-ust/liblttng-ust/./jhash.h:129:15<br /> #1 0x7f1e9d160322 in jhash /home/efficios/git/lttng-ust/liblttng-ust/./jhash.h:256:9<br /> #2 0x7f1e9d1657a2 in add_callsite /home/efficios/git/lttng-ust/liblttng-ust/tracepoint.c:422:9<br /> #3 0x7f1e9d15d518 in lib_register_callsites /home/efficios/git/lttng-ust/liblttng-ust/tracepoint.c:552:3<br /> #4 0x7f1e9d15ca91 in tracepoint_register_lib /home/efficios/git/lttng-ust/liblttng-ust/tracepoint.c:903:2<br /> #5 0x7f1e9d4a124e in _<em>tracepoints</em>_ptrs_init /home/efficios/git/lttng-ust/liblttng-ust/../include/lttng/tracepoint.h:485:3<br /> #6 0x7f1e9d4a2d8d in lttng_ust_statedump_init /home/efficios/git/lttng-ust/liblttng-ust/lttng-ust-statedump.c:645:2<br /> <a class="issue tracker-1 status-5 priority-5 priority-high2 closed" title="Bug: Double PID registering and unregistering race (Resolved)" href="https://bugs.lttng.org/issues/7">#7</a> 0x7f1e9d409a85 in lttng_ust_init /home/efficios/git/lttng-ust/liblttng-ust/lttng-ust-comm.c:1846:2<br /> #8 0x7f1e9d7e0732 (/lib64/ld-linux-x86-64.so.2+0x10732)<br /> <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: LTTng-UST java jni wrapper does not build with OpenJDK (Resolved)" href="https://bugs.lttng.org/issues/9">#9</a> 0x7f1e9d7d10c9 (/lib64/ld-linux-x86-64.so.2+0x10c9)</p>
<p>0x7f1e9d589270 is located 48 bytes to the left of global variable '__tp_strtab_lttng_ust_lib___build_id' defined in './ust_lib.h:55:1' (0x7f1e9d5892a0) of size 23<br /> '__tp_strtab_lttng_ust_lib___build_id' is ascii string 'lttng_ust_lib:build_id'<br />0x7f1e9d589273 is located 0 bytes to the right of global variable '__tp_strtab_lttng_ust_lib___load' defined in './ust_lib.h:42:1' (0x7f1e9d589260) of size 19<br /> '__tp_strtab_lttng_ust_lib___load' is ascii string 'lttng_ust_lib:load'<br />SUMMARY: AddressSanitizer: global-buffer-overflow /home/efficios/git/lttng-ust/liblttng-ust/./jhash.h:129:15 in hashlittle<br />Shadow bytes around the buggy address:<br /> 0x0fe453aa91f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br /> 0x0fe453aa9200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br /> 0x0fe453aa9210: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br /> 0x0fe453aa9220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br /> 0x0fe453aa9230: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br />=>0x0fe453aa9240: 00 00 00 00 00 00 00 00 00 00 00 00 00 00<sup><a href="#fn03">03</a></sup>f9<br /> 0x0fe453aa9250: f9 f9 f9 f9 00 00 07 f9 f9 f9 f9 f9 00 00 00 01<br /> 0x0fe453aa9260: f9 f9 f9 f9 00 00 05 f9 f9 f9 f9 f9 00 00 00 02<br /> 0x0fe453aa9270: f9 f9 f9 f9 00 00 00 05 f9 f9 f9 f9 00 00 00 05<br /> 0x0fe453aa9280: f9 f9 f9 f9 00 00 00 07 f9 f9 f9 f9 00 00 00 05<br /> 0x0fe453aa9290: f9 f9 f9 f9 00 00 00 f9 f9 f9 f9 f9 00 00 07 f9<br />Shadow byte legend (one shadow byte represents 8 application bytes):<br /> Addressable: 00<br /> Partially addressable: 01 02 03 04 05 06 07 <br /> Heap left redzone: fa<br /> Freed heap region: fd<br /> Stack left redzone: f1<br /> Stack mid redzone: f2<br /> Stack right redzone: f3<br /> Stack after return: f5<br /> Stack use after scope: f8<br /> Global redzone: f9<br /> Global init order: f6<br /> Poisoned by user: f7<br /> Container overflow: fc<br /> Array cookie: ac<br /> Intra object redzone: bb<br /> ASan internal: fe<br /> Left alloca redzone: ca<br /> Right alloca redzone: cb<br /> Shadow gap: cc<br />5772ABORTING</p> LTTng-modules - Feature #962 (New): add x86 exceptions.h and irq_vectors.h instrumentation (and m...https://bugs.lttng.org/issues/9622015-10-22T19:47:19ZMathieu Desnoyersmathieu.desnoyers@efficios.comLTTng-modules - Bug #943 (Resolved): All events are filtered-out when using a wildcard in a filte...https://bugs.lttng.org/issues/9432015-09-29T16:50:20ZJérémie Galarneaujeremie.galarneau@efficios.com
<p>While applying a filter to syscalls of the form:<br /><pre>
$ lttng enable-event --kernel --syscall --all --filter 'filename == "*"'
[12:46:10.047113455] (+0.009323468) XThink syscall_entry_open: { cpu_id = 1 }, { filename = "/home/jgalar/.config/chromium/Default", flags = 524288, mode = 420 }
[12:46:10.615910212] (+0.568796757) XThink syscall_entry_open: { cpu_id = 2 }, { filename = "/home/jgalar/.config/chromium/Default/.org.chromium.Chromium.nMsMbS", flags = 194, mode = 384 }
[12:46:10.615965534] (+0.000055322) XThink syscall_entry_open: { cpu_id = 2 }, { filename = "/home/jgalar/.config/chromium/Default/.org.chromium.Chromium.nMsMbS", flags = 1, mode = 384 }
</pre></p>
<p>works, it seems that a more complex string results in no events being traced.</p>
<pre>
$ lttng enable-event --kernel --syscall --all --filter 'filename == "/home/jgalar*"'
... no events!
</pre> LTTng-tools - Feature #921 (Resolved): add tests for lttng-modules filterhttps://bugs.lttng.org/issues/9212015-09-01T18:07:24ZJérémie Galarneaujeremie.galarneau@efficios.comLTTng-tools - Feature #920 (Resolved): add tests for lttng-modules wildcardshttps://bugs.lttng.org/issues/9202015-09-01T18:07:01ZJérémie Galarneaujeremie.galarneau@efficios.comLTTng-modules - Bug #858 (Resolved): babeltrace cannot parse following on mips. I think second re...https://bugs.lttng.org/issues/8582014-11-11T14:20:12ZUmut Tezduyarumut@tezduyar.com
<p>lttng enable-channel syscalls --kernel --num-subbuf 16 $SESSION<br />lttng add-context $SESSION -c syscalls -k --type pid --type tid<br />lttng add-context $SESSION -c syscalls -k -t prio -t perf:cpu:cycles<br />lttng enable-event --kernel --syscall -a $SESSION -c syscalls</p>
<p>syscalls_0 100% 808KB 808.0KB/s 00:00 <br />syscalls_0.idx 100% 296 0.3KB/s 00:00 <br />syscalls_1.idx 100% 184 0.2KB/s 00:00 <br />syscalls_1 100% 392KB 392.0KB/s 00:00 l<br />metadata 100% 92KB 92.0KB/s 00:00</p>
<p>umut$ babeltrace kernel/<br />[15:09:14.976549620] (+?.?????????) axis-00408cc5a889 exit_syscall: { cpu_id = 0 }, { pid = 2523, tid = 2527, prio = 20, perf_cpu_cycles = 288705510 }, { ret = 1 }<br />[15:09:14.976811465] (+0.000261845) axis-00408cc5a889 sys_ioctl: { cpu_id = 0 }, { pid = 2527, tid = 20, prio = 288798108, perf_cpu_cycles = 2306113510548963354 }, { fd = 1, cmd = 2, arg = 3726872232 }<br />[error] Event id 2523 is outside range.<br />[error] Reading event failed.<br />Error printing trace.</p>
<p>umuttl@lnxumuttl:umut$ babeltrace --version<br />Error parsing options.</p>
<p>BabelTrace Trace Viewer and Converter 1.2.2</p> LTTng-UST - Bug #851 (Resolved): Add perf event context on unsupported architectureshttps://bugs.lttng.org/issues/8512014-10-29T17:56:15ZCharles Brierec.briere@samsung.com
<p>When adding a perf counter to the context on an architecture that doesn't support it, I would expect lttng add-context to return me an error, but it tells me it has been added to every channels.</p>
<p>I ran into that issue on a Galaxy Note 3 (ARM based) running Android. Although I don't have any other ARM board I can try this on at the moment.</p>
<p>It can be reproduced as followed :</p>
<pre>
$ lttng create
Session auto-20090221-085733 created.
Traces will be written in /sdcard/lttng-traces/auto-20090221-085733
$ lttng enable-event -ua
All UST events are enabled in channel channel0
$ lttng add-context -u -t perf:thread:cycles
UST context perf:thread:cycles added to all channels
</pre>
<p>Following in a a log of the sessiond -vvv for each commands which doesn't show any error (unfortunately)</p>
<p>lttng create</p>
<pre>
DEBUG1 - 08:57:33.144723 [13186/13243]: Wait for client response (in thread_manage_clients() at main.c:4061)
DEBUG1 - 08:57:33.144991 [13186/13243]: Receiving data from client ... (in thread_manage_clients() at main.c:4106)
DEBUG1 - 08:57:33.146169 [13186/13243]: Nothing recv() from client... continuing (in thread_manage_clients() at main.c:4110)
DEBUG1 - 08:57:33.146350 [13186/13243]: Clean command context structure (in clean_command_ctx() at main.c:739)
DEBUG1 - 08:57:33.146410 [13186/13243]: Accepting client command ... (in thread_manage_clients() at main.c:4019)
DEBUG1 - 08:57:33.148955 [13186/13243]: Wait for client response (in thread_manage_clients() at main.c:4061)
DEBUG1 - 08:57:33.149141 [13186/13243]: Receiving data from client ... (in thread_manage_clients() at main.c:4106)
DEBUG1 - 08:57:33.149967 [13186/13243]: Processing client command 8 (in process_client_msg() at main.c:2779)
DEBUG1 - 08:57:33.150108 [13186/13243]: Waiting for 1 URIs from client ... (in process_client_msg() at main.c:3436)
DEBUG2 - 08:57:33.151095 [13186/13243]: Trying to find session by name auto-20090221-085733 (in session_find_by_name() at session.c:169)
DEBUG3 - 08:57:33.151271 [13186/13243]: Created hashtable size 4 at 0x12ad190 of type 1 (in lttng_ht_new() at hashtable.c:127)
DEBUG1 - 08:57:33.151336 [13186/13243]: Tracing session auto-20090221-085733 created with ID 5 by UID 0 GID 0 (in session_create() at session.c:276)
DEBUG2 - 08:57:33.151387 [13186/13243]: Trying to find session by name auto-20090221-085733 (in session_find_by_name() at session.c:169)
DEBUG3 - 08:57:33.151458 [13186/13243]: Created hashtable size 4 at 0x12a7b80 of type 1 (in lttng_ht_new() at hashtable.c:127)
DEBUG2 - 08:57:33.151517 [13186/13243]: Setting trace directory path from URI to /sdcard/lttng-traces/auto-20090221-085733 (in add_uri_to_consumer() at cmd.c:515)
DEBUG1 - 08:57:33.151592 [13186/13243]: Sending response (size: 16, retcode: Success) (in thread_manage_clients() at main.c:4155)
DEBUG1 - 08:57:33.151709 [13186/13243]: Clean command context structure (in clean_command_ctx() at main.c:739)
DEBUG1 - 08:57:33.151764 [13186/13243]: Accepting client command ... (in thread_manage_clients() at main.c:4019)
</pre>
<p>lttng enable-event -ua</p>
<pre>
DEBUG1 - 08:57:45.734624 [13186/13243]: Wait for client response (in thread_manage_clients() at main.c:4061)
DEBUG1 - 08:57:45.734884 [13186/13243]: Receiving data from client ... (in thread_manage_clients() at main.c:4106)
DEBUG1 - 08:57:45.735975 [13186/13243]: Nothing recv() from client... continuing (in thread_manage_clients() at main.c:4110)
DEBUG1 - 08:57:45.736162 [13186/13243]: Clean command context structure (in clean_command_ctx() at main.c:739)
DEBUG1 - 08:57:45.736224 [13186/13243]: Accepting client command ... (in thread_manage_clients() at main.c:4019)
DEBUG1 - 08:57:45.738073 [13186/13243]: Wait for client response (in thread_manage_clients() at main.c:4061)
DEBUG1 - 08:57:45.738255 [13186/13243]: Receiving data from client ... (in thread_manage_clients() at main.c:4106)
DEBUG1 - 08:57:45.739052 [13186/13243]: Processing client command 6 (in process_client_msg() at main.c:2779)
DEBUG1 - 08:57:45.739167 [13186/13243]: Getting session auto-20090221-085733 by name (in process_client_msg() at main.c:2862)
DEBUG2 - 08:57:45.739221 [13186/13243]: Trying to find session by name auto-20090221-085733 (in session_find_by_name() at session.c:169)
DEBUG1 - 08:57:45.739280 [13186/13243]: Creating UST session (in create_ust_session() at main.c:2659)
DEBUG3 - 08:57:45.739375 [13186/13243]: Created hashtable size 4 at 0x12a0b68 of type 0 (in lttng_ht_new() at hashtable.c:127)
DEBUG3 - 08:57:45.739444 [13186/13243]: Created hashtable size 4 at 0x12acfd8 of type 2 (in lttng_ht_new() at hashtable.c:127)
DEBUG3 - 08:57:45.739541 [13186/13243]: Created hashtable size 4 at 0x12a8548 of type 1 (in lttng_ht_new() at hashtable.c:127)
DEBUG2 - 08:57:45.739594 [13186/13243]: UST trace session create successful (in trace_ust_create_session() at trace-ust.c:289)
DEBUG3 - 08:57:45.739644 [13186/13243]: Copying tracing session consumer output in UST session (in copy_session_consumer() at main.c:2607)
DEBUG3 - 08:57:45.739785 [13186/13243]: Created hashtable size 4 at 0x12a8760 of type 1 (in lttng_ht_new() at hashtable.c:127)
DEBUG3 - 08:57:45.739904 [13186/13243]: Copy session consumer subdir /ust (in copy_session_consumer() at main.c:2625)
DEBUG3 - 08:57:45.740004 [13186/13243]: Consumer socket created (fd: 41) and added to output (in consumer_create_socket() at consumer.c:301)
DEBUG1 - 08:57:45.740067 [13186/13243]: Setting relayd for session auto-20090221-085733 (in cmd_setup_relayd() at cmd.c:756)
DEBUG1 - 08:57:45.740124 [13186/13243]: Enable event command for event '*' (in cmd_enable_event() at cmd.c:1402)
DEBUG2 - 08:57:45.740318 [13186/13243]: Trace UST channel channel0 not found by name (in trace_ust_find_channel_by_name() at trace-ust.c:162)
DEBUG1 - 08:57:45.740388 [13186/13243]: Enabling channel for session auto-20090221-085733 (in cmd_enable_channel() at cmd.c:944)
DEBUG2 - 08:57:45.740442 [13186/13243]: Trace UST channel channel0 not found by name (in trace_ust_find_channel_by_name() at trace-ust.c:162)
DEBUG3 - 08:57:45.740515 [13186/13243]: Created hashtable size 4 at 0x12addf8 of type 0 (in lttng_ht_new() at hashtable.c:127)
DEBUG3 - 08:57:45.740575 [13186/13243]: Created hashtable size 4 at 0x12ae010 of type 1 (in lttng_ht_new() at hashtable.c:127)
DEBUG2 - 08:57:45.740623 [13186/13243]: Trace UST channel channel0 created (in trace_ust_create_channel() at trace-ust.c:357)
DEBUG2 - 08:57:45.740676 [13186/13243]: Channel channel0 is being created for UST with buffer 1 and id 0 (in channel_ust_create() at channel.c:348)
DEBUG2 - 08:57:45.740728 [13186/13243]: UST app adding channel channel0 to UST domain for session id 5 (in ust_app_create_channel_glb() at ust-app.c:3555)
DEBUG2 - 08:57:45.740794 [13186/13243]: Channel channel0 created successfully (in channel_ust_create() at channel.c:383)
DEBUG2 - 08:57:45.740852 [13186/13243]: Trace UST channel channel0 found by name (in trace_ust_find_channel_by_name() at trace-ust.c:157)
DEBUG2 - 08:57:45.740906 [13186/13243]: Trace UST event * NOT found (in trace_ust_find_event() at trace-ust.c:198)
DEBUG2 - 08:57:45.740961 [13186/13243]: Trace UST event *, loglevel (0,-1) created (in trace_ust_create_event() at trace-ust.c:433)
DEBUG1 - 08:57:45.741011 [13186/13243]: UST app creating event * for all apps for session id 5 (in ust_app_create_event_glb() at ust-app.c:3706)
DEBUG1 - 08:57:45.741070 [13186/13243]: Event UST * created in channel channel0 (in event_ust_enable_tracepoint() at event.c:472)
DEBUG1 - 08:57:45.741128 [13186/13243]: Sending response (size: 16, retcode: Success) (in thread_manage_clients() at main.c:4155)
DEBUG1 - 08:57:45.741257 [13186/13243]: Clean command context structure (in clean_command_ctx() at main.c:739)
DEBUG1 - 08:57:45.741314 [13186/13243]: Accepting client command ... (in thread_manage_clients() at main.c:4019)
DEBUG3 - 08:57:45.741659 [13186/13241]: [ht-thread] Polling on 2 fds. (in thread_ht_cleanup() at ht-cleanup.c:64)
</pre>
<p>lttng add-context -u -t perf:thread:cycles</p>
<pre>
DEBUG1 - 08:57:54.629061 [13186/13243]: Wait for client response (in thread_manage_clients() at main.c:4061)
DEBUG1 - 08:57:54.633314 [13186/13243]: Receiving data from client ... (in thread_manage_clients() at main.c:4106)
DEBUG1 - 08:57:54.649128 [13186/13243]: Nothing recv() from client... continuing (in thread_manage_clients() at main.c:4110)
DEBUG1 - 08:57:54.653703 [13186/13243]: Clean command context structure (in clean_command_ctx() at main.c:739)
DEBUG1 - 08:57:54.654819 [13186/13243]: Accepting client command ... (in thread_manage_clients() at main.c:4019)
DEBUG1 - 08:57:54.684376 [13186/13243]: Wait for client response (in thread_manage_clients() at main.c:4061)
DEBUG1 - 08:57:54.687063 [13186/13243]: Receiving data from client ... (in thread_manage_clients() at main.c:4106)
DEBUG1 - 08:57:54.700304 [13186/13243]: Processing client command 0 (in process_client_msg() at main.c:2779)
DEBUG1 - 08:57:54.703358 [13186/13243]: Getting session auto-20090221-085733 by name (in process_client_msg() at main.c:2862)
DEBUG2 - 08:57:54.704354 [13186/13243]: Trying to find session by name auto-20090221-085733 (in session_find_by_name() at session.c:169)
DEBUG3 - 08:57:54.705913 [13186/13243]: Consumer socket created (fd: 41) and added to output (in consumer_create_socket() at consumer.c:301)
DEBUG1 - 08:57:54.706842 [13186/13243]: Setting relayd for session auto-20090221-085733 (in cmd_setup_relayd() at cmd.c:756)
DEBUG1 - 08:57:54.708661 [13186/13243]: Context UST 5 added to channel channel0 (in add_uctx_to_channel() at context.c:134)
DEBUG1 - 08:57:54.709644 [13186/13243]: Sending response (size: 16, retcode: Success) (in thread_manage_clients() at main.c:4155)
DEBUG1 - 08:57:54.711559 [13186/13243]: Clean command context structure (in clean_command_ctx() at main.c:739)
DEBUG1 - 08:57:54.712524 [13186/13243]: Accepting client command ... (in thread_manage_clients() at main.c:4019)
</pre> Babeltrace - Bug #724 (Resolved): babeltrace of flight recorder trace undergoes time warp?https://bugs.lttng.org/issues/7242014-01-23T14:52:47ZDaniel U. Thibaultdaniel.thibault@drdc-rddc.gc.ca
<p>Assume a flight recorder trace is generated like this:<br /><pre>
$ lttng create limkern
Session limkern created
Traces will be written in /home/daniel/lttng-traces/limkern-20140123-085831
$ lttng enable-channel channel0 -k --tracefile-size 262144 --tracefile-count 1
Kernel channel channel0 enabled for session limkern
$ lttng enable-event -k --all -c channel0
All kernel events are enabled in channel channel0
$ lttng start
(wait for a while)
$ lttng stop
</pre></p>
<p>Now when this is babeltraced:</p>
<pre>
$ babeltrace /home/daniel/lttng-traces/limkern-20140123-085831 -n all -f all -v -w /home/daniel/lttng-traces/limkern_nafav
[verbose] Verbose mode active
[...]
[warning] Tracer discarded 378942 events between [09:00:44.643712446] and [09:00:44.643710896] in trace UUID ce[...]22, at path: "/home/daniel/lttng-traces/limkern-20140123-085831/kernel", within stream id 0, at relative path: "channel_0_0_0". You should consider recording a new trace with larger buffers or with fewer events enabled.
[verbose] finished converting. Output written to:
/home/daniel/lttng-traces/limkern_nafav
</pre>
<p>Note how the lost events are said to lie in a nonsensical time span where the end (44.64371*0896*) is <strong>before</strong> the start (44.64371*2446*).</p>
<p>Using babeltrace 1.1.1-31-513413e.</p>
<p>Related to bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Lost events time ranges may be offset (Resolved)" href="https://bugs.lttng.org/issues/589">#589</a>?</p> LTTng-modules - Bug #696 (Resolved): ARM gcc 4.8.0, 4.8.1, 4.8.2 produces clobbered frame accesseshttps://bugs.lttng.org/issues/6962013-11-24T08:45:51ZMathieu Desnoyersmathieu.desnoyers@efficios.com
<p>see <a class="external" href="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58854">http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58854</a></p>
<p>fixed by:</p>
<p>commit cf262f57baebeb3db47b4a44d0ab153b4d2abb2d<br />Author: Mathieu Desnoyers <<a class="email" href="mailto:mathieu.desnoyers@efficios.com">mathieu.desnoyers@efficios.com</a>><br />Date: Sun Nov 24 03:42:22 2013 -0500</p>
<pre><code>gcc blacklist: only apply when building with gcc</code></pre>
<pre><code>Signed-off-by: Mathieu Desnoyers &lt;<a class="email" href="mailto:mathieu.desnoyers@efficios.com">mathieu.desnoyers@efficios.com</a>&gt;</code></pre>
<p>commit 40d6e366189861b779fcc012f10a5abebebf5ea9<br />Author: Mathieu Desnoyers <<a class="email" href="mailto:mathieu.desnoyers@efficios.com">mathieu.desnoyers@efficios.com</a>><br />Date: Sun Nov 24 03:28:10 2013 -0500</p>
<pre><code>Blacklist ARM gcc 4.8.0, 4.8.1, 4.8.2</code></pre>
<pre><code>Signed-off-by: Mathieu Desnoyers &lt;<a class="email" href="mailto:mathieu.desnoyers@efficios.com">mathieu.desnoyers@efficios.com</a>&gt;</code></pre>
<p>Triggers on stress-test with tracing active, with IRQ nesting on top of 1 instruction window.</p> LTTng-UST - Bug #626 (Resolved): assertion in libust cause application to quithttps://bugs.lttng.org/issues/6262013-09-05T18:23:09ZYannick Brosseauyannick.brosseau@polymtl.ca
<p>I'm instrumenting RSyslog and I sometime get the following output and assert:</p>
<pre>
libust[4357/4358]: Error: sendmsg: Socket operation on non-socket (in ustcomm_send_unix_sock() at lttng-ust-comm.c:332)
libust[4357/4358]: Error: Socket shutdown error (in ustcomm_send_unix_sock() at lttng-ust-comm.c:339)
libust[4357/4358]: Error: Error handling message for global socket (in ust_listener_thread() at lttng-ust-comm.c:1087)
libust[4357/4358]: Error: recvmsg: Socket operation on non-socket (in ustcomm_recv_unix_sock() at lttng-ust-comm.c:285)
libust[4357/4358]: Error: Socket shutdown error (in ustcomm_recv_unix_sock() at lttng-ust-comm.c:292)
libringbuffer[4357/4358]: Error: close: Bad file descriptor (in shmp_object_destroy() at shm.c:414)
rsyslogd: shm.c:415: shmp_object_destroy: Assertion `0' failed.
</pre><br />This happens when I issue a lttng stop command. <br />It also shows sometime when I try to start the application.
<p>I run the app with the following command:<br />LD_PRELOAD=liblttng-ust-fork.so /usr/local/sbin/rsyslogd</p>
<p>I did not see the problem when I run in rsyslog non fork mode.</p>
<p>Currently running both 2.3 for lttng-ust and lttng-tools. Same problem was happening on 2.2</p> Babeltrace - Bug #361 (Resolved): activate the test in make checkhttps://bugs.lttng.org/issues/3612012-10-02T22:46:37ZYannick Brosseauyannick.brosseau@polymtl.ca
<p>Currently, the make check does nothing.</p>
<p>We should:<br />1-Run the test-bitfield<br />2-run babeltrace with the test tracefiles in tests/ctf-traces</p> LTTng-tools - Feature #281 (Resolved): Add event filtering features in session daemonhttps://bugs.lttng.org/issues/2812012-06-20T19:37:57ZDavid GouletBabeltrace - Bug #239 (Resolved): Babeltrace ignores errors for an app when conversion for other ...https://bugs.lttng.org/issues/2392012-05-25T20:56:23ZJesus Garciajesus.garcia@ericsson.com
<p>Hi Guys,</p>
<p>We have found the following issue in Babeltrace rc2:</p>
<p>When running babeltrace over a session directory containing several directories for several apps, babeltrace does not notice that there are issues with one of the apps.<br />In this particular case the issue is that one of the apps (let's call it appX) does not have a metadata file. The CTF files are fine.<br />Here is the result:</p>
<p>SC-1:/home/trace # babeltrace TRACact008_1/SC-1 > /tmp/deleteme.txt<br />SC-1:/home/trace # echo $?<br />0<br />SC-1:/home/trace # ll /tmp/deleteme.txt<br /><del>rw-r--r-</del> 1 root root 1087710 May 25 16:47 /tmp/deleteme.txt <<=====<< babeltrace converted everything else from the other apps<br />SC-1:/home/trace #</p>
<p>However, when running babeltrace for appX only, it does produce errors:</p>
<p>SC-1:/home/trace # babeltrace TRACact008_1/SC-1/ust/TestApp_type1-12988-20120525-162422/ > /tmp/deleteme.txt<br />[error] Cannot open any trace for reading.</p>
<p>[error] opening trace "TRACact008_1/SC-1/ust/TestApp_type1-12988-20120525-162422/" for reading.</p>
<p>SC-1:/home/trace # echo $?<br />1<br />SC-1:/home/trace # ll /tmp/deleteme.txt<br /><del>rw-r--r-</del> 1 root root 0 May 25 16:49 /tmp/deleteme.txt<br />SC-1:/home/trace #</p>
<p>So, when converting the whole session babeltrace should convert what it can (as it did), but then also report any errors and return 1 as error code.</p>
<p>Thanks,<br />Jesus</p> Babeltrace - Bug #222 (Resolved): BabelTrace 1.0.0-rc1 does not report an error code in error sit...https://bugs.lttng.org/issues/2222012-04-24T15:04:50ZJesus Garciajesus.garcia@ericsson.com
<p>Hi Guys,</p>
<p>The latest version of babeltrace (rc1) does not report an error code in error situations (at least not this particular error).<br />In the following example there is a text file in the Pid directory and when babeltrace is invoked, it reports an error, but it returns 0:</p>
<p>SC-1:~ # ll /home/trace/Profile016_1/SC-1/ust/TestApp_type1-4459-20120423-231455/<br />total 20<br /><del>rw-r--r-</del> 1 root root 0 Apr 23 23:16 MyTextFile.txt<br /><del>rw-r--r-</del> 1 root root 0 Apr 23 23:16 MyTextFile2.txt<br />-rwxrwxrwx 1 root root 4096 Apr 23 23:15 channel0_0<br />-rwxrwxrwx 1 root root 4096 Apr 23 23:15 channel0_1<br />-rwxrwxrwx 1 root root 4096 Apr 23 23:15 channel0_2<br />-rwxrwxrwx 1 root root 4096 Apr 23 23:15 channel0_3<br />-rwxrwxrwx 1 root root 4096 Apr 23 23:15 metadata<br />SC-1:~ # babeltrace /home/trace/Profile016_1/SC-1/ust/TestApp_type1-4459-20120423-231455/<br />[error] Open file stream error.<br />[warning] [Context] Cannot open_trace of the format /home/trace/Profile016_1/SC-1/ust/TestApp_type1-4459-20120423-231455/ .</p>
<p>[warning] [Context] opening trace "/home/trace/Profile016_1/SC-1/ust/TestApp_type1-4459-20120423-231455/" from /home/trace/Profile016_1/SC-1/ust/TestApp_type1-4459-20120423-231455/ for reading.<br />SC-1:~ # echo $?<br />0<br />SC-1:~ # babeltrace -h<br />BabelTrace Trace Viewer and Converter 1.0.0-rc1</p>
<p>======================================================================</p>
<p>In the previous version of babaltrace, it reports the same errors, but it returns 1:</p>
<p>SC-1:/home/trace/Profile006_4/SC-1/ust # babeltrace /home/trace/Profile006_4/SC-1/ust/TestApp_type1-16635-20120424-101632/<br />[error] Open file stream error.<br />[error] [Context] Cannot open_trace of the format /home/trace/Profile006_4/SC-1/ust/TestApp_type1-16635-20120424-101632/ .</p>
<p>[error] [Context] opening trace "/home/trace/Profile006_4/SC-1/ust/TestApp_type1-16635-20120424-101632/" from /home/trace/Profile006_4/SC-1/ust/TestApp_type1-16635-20120424-101632/ for reading.<br />[error] opening trace "/home/trace/Profile006_4/SC-1/ust/TestApp_type1-16635-20120424-101632/" for reading.</p>
<p>SC-1:/home/trace/Profile006_4/SC-1/ust # echo $?<br />1<br />SC-1:/home/trace/Profile006_4/SC-1/ust # babeltrace --help<br />BabelTrace Trace Viewer and Converter 1.0.0-pre4</p> LTTng-modules - Bug #52 (Resolved): Add missing instrumentationhttps://bugs.lttng.org/issues/522012-02-16T16:05:54ZJulien Desfossezjdesfossez@efficios.com
<p>We are missing some important trace events that will be very useful :<br />- timer<br />- signal<br />- workqueue<br />- power</p>