LTTng bugs repository: Issueshttps://bugs.lttng.org/https://bugs.lttng.org/themes/lttng/favicon/a.ico?14249722912012-03-13T20:36:10ZLTTng bugs repository
Redmine LTTng-modules - Bug #169 (Resolved): Lttng Kernel Module: Timestamp offset invalid on a 32 bit OShttps://bugs.lttng.org/issues/1692012-03-13T20:36:10ZMatthew Khouzam
<p>In the metadata of a kernel trace we have the following clock descriptor: <br />clock {<br /> name = monotonic;<br /> uuid = "ed4eb84f-b43c-4133-8db8-28203028f97b";<br /> description = "Monotonic Clock";<br /> freq = 1000000000; /* Frequency, in Hz <strong>/<br /> /</strong> clock value offset from Epoch is: offset * (1/freq) */<br /> offset = 18445690674791632402;<br />};</p>
<p>The offset is too high, it should be <br />clock {<br /> name = monotonic;<br /> uuid = "ed4eb84f-b43c-4133-8db8-28203028f97b";<br /> description = "Monotonic Clock";<br /> freq = 1000000000; /* Frequency, in Hz <strong>/<br /> /</strong> clock value offset from Epoch is: offset * (1/freq) */<br /> offset = 1330617403233586776;<br />};<br />Like in UST.</p> LTTng-UST - Bug #142 (Resolved): Python application freeze when registering to sessiondhttps://bugs.lttng.org/issues/1422012-03-01T15:30:40ZYannick Brosseauyannick.brosseau@polymtl.ca
<p>A python application freeze when we try to start it.</p>
<p>We get the following error message on the console:<br />libust[11028/11028]: Error: Timed out waiting for ltt-sessiond (in lttng_ust_init() at lttng-ust-comm.c:873)</p>
<p>The corresponding output of lttng-sessiond -vvv:</p>
<p>DEBUG1: Accepting client command ... [in thread_manage_clients() at main.c:3627]<br />DEBUG1: UST registration received with pid:11028 ppid:11027 uid:0 gid:0 sock:19 name:python (version 2.0) [in thread_registration_apps() at main.c:1392]<br />DEBUG1: Futex n to 1 wake done [in futex_nto1_wake() at futex.c:101]<br />DEBUG1: Accepting application registration [in thread_registration_apps() at main.c:1322]<br />DEBUG1: Futex n to 1 wait done [in futex_nto1_wait() at futex.c:88]<br />DEBUG1: Futex n to 1 prepare done [in futex_nto1_prepare() at futex.c:74]<br />DEBUG1: Dispatching UST registration pid:11028 ppid:11027 uid:0 gid:0 sock:19 name:python (version 2.0) [in thread_dispatch_ust_registration() at main.c:1245]<br />DEBUG1: Woken up but nothing in the UST command queue [in thread_dispatch_ust_registration() at main.c:1233]<br />DEBUG3: Created hashtable size 4 at 0x21ba4b0 of type 1 [in lttng_ht_new() at hashtable.c:96]<br />DEBUG1: App registered with pid:11028 ppid:11027 uid:0 gid:0 sock:19 name:python (version 2.0) [in ust_app_register() at ust-app.c:1317]<br />DEBUG2: UST app PID 11028 is compatible with major version 2 (supporting <= 2) [in ust_app_validate_version() at ust-app.c:2562]<br />DEBUG2: UST app global update for app sock 19 for session id 1 [in ust_app_global_update() at ust-app.c:2232]<br />DEBUG2: UST app pid: 11028 session id 1 not found, creating it [in create_ust_app_session() at ust-app.c:855]<br />DEBUG3: Created hashtable size 4 at 0x21bb7b0 of type 0 [in lttng_ht_new() at hashtable.c:96]<br />DEBUG2: Shadow copy of session handle -1 [in shadow_copy_session() at ust-app.c:766]<br />DEBUG2: Channel channel0 not found on shadow session copy, creating it [in shadow_copy_session() at ust-app.c:795]<br />DEBUG3: Created hashtable size 4 at 0x21bc5c0 of type 1 [in lttng_ht_new() at hashtable.c:96]<br />DEBUG3: Created hashtable size 4 at 0x21bc860 of type 0 [in lttng_ht_new() at hashtable.c:96]<br />DEBUG3: UST app channel channel0 allocated [in alloc_ust_app_channel() at ust-app.c:281]<br />DEBUG2: UST app shadow copy of channel channel0 started [in shadow_copy_channel() at ust-app.c:706]<br />DEBUG2: UST event * not found on shadow copy channel [in shadow_copy_channel() at ust-app.c:733]<br />DEBUG3: Created hashtable size 4 at 0x21bce90 of type 1 [in lttng_ht_new() at hashtable.c:96]<br />DEBUG3: UST app event * allocated [in alloc_ust_app_event() at ust-app.c:316]<br />DEBUG3: UST app shadow copy of channel channel0 done [in shadow_copy_channel() at ust-app.c:743]</p> Babeltrace - Bug #82 (Resolved): Need to generically print tracer version info in verbose modehttps://bugs.lttng.org/issues/822012-02-20T20:26:21ZMathieu Desnoyersmathieu.desnoyers@efficios.comLTTng-modules - Bug #81 (Resolved): Need to standardize versioning across toolchainhttps://bugs.lttng.org/issues/812012-02-20T19:54:51ZMathieu Desnoyersmathieu.desnoyers@efficios.comLTTng-UST - Bug #80 (Resolved): Need to standardize versioning across toolchainhttps://bugs.lttng.org/issues/802012-02-20T19:54:25ZMathieu Desnoyersmathieu.desnoyers@efficios.comLTTng-tools - Bug #79 (Resolved): Need to standardize versioning across toolchainhttps://bugs.lttng.org/issues/792012-02-20T19:53:37ZMathieu Desnoyersmathieu.desnoyers@efficios.comLTTng-UST - Bug #58 (Won't fix): sched_getcpu triggers a system call on glibc older than 2.14https://bugs.lttng.org/issues/582012-02-16T21:35:49ZMathieu Desnoyersmathieu.desnoyers@efficios.com
<p>tracing "hello" with kernel tracing enabled lets us discover that sched_getcpu, supposed to be a vDSO, actually triggers a system call:</p>
<p>[16:05:32.991027867] (+0.000000909) ust_tests_hello:tptest: { 1 }, { intfield = 9, intfield2 = 0x9, longfield = 9, netintfield = 9, netintfieldhex = 0x9, arrfield1 = [ [0] = 1, [1] = 2, [2] = 3 ], arrfield2 = "test", _seqfield1_length = 4, seqfield1 = [ [0] = 116, [1] = 101, [2] = 115, [3] = 116 ], _seqfield2_length = 4, seqfield2 = "test", stringfield = "test", floatfield = 2222, doublefield = 2 }<br />[16:05:32.991029728] (+0.000001861) sys_getcpu: { 1 }, { cpup = 0x7FFF1B010350, nodep = 0x0, tcache = 0x7FC76A03E7D8 }<br />[16:05:32.991033220] (+0.000003492) exit_syscall: { 1 }, { ret = 0 }<br />[16:05:32.991034256] (+0.000001036) ust_tests_hello:tptest: { 1 }, { intfield = 10, intfield2 = 0xA, longfield = 10, netintfield = 10, netintfieldhex = 0xA, arrfield1 = [ [0] = 1, [1] = 2, [2] = 3 ], arrfield2 = "test", _seqfield1_length = 4, seqfield1 = [ [0] = 116, [1] = 101, [2] = 115, [3] = 116 ], _seqfield2_length = 4, seqfield2 = "test", stringfield = "test", floatfield = 2222, doublefield = 2 }<br />[16:05:32.991036204] (+0.000001948) sys_getcpu: { 1 }, { cpup = 0x7FFF1B010350, nodep = 0x0, tcache = 0x7FC76A03E7D8 }<br />[16:05:32.991036936] (+0.000000732) exit_syscall: { 1 }, { ret = 0 }</p>
<p>It will need to be investigated at the glibc and kernel level, and maybe we will have to implement our own wrapper over the vDSO.</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> LTTng-tools - Bug #46 (Resolved): Install lttng-consumerd in libdir/lttnghttps://bugs.lttng.org/issues/462012-02-14T17:12:15ZDavid Goulet
<p>The lttng-consumerd should not be used by the user so it should not be install in the $(bindir) directory.</p>
<p>We have to install it to $(libdir)/lttng/ and make sure the session daemon use this location.</p> LTTng-UST - Bug #44 (Resolved): implicit declaration of function 'sched_getcpu'https://bugs.lttng.org/issues/442012-02-12T06:48:06ZAnonymous
<p>While compiling latest lttng-ust git HEAD, I'm getting the following warnings (see attached build log):<br />warning: implicit declaration of function 'sched_getcpu' [-Wimplicit-function-declaration]<br />which usually indicate a function simply doesn't exist.</p>
<p>This might be due to the new eglibc version in Ubuntu 12.04, which is 2.15. Compared to 2.13 currently in Debian Sid and Ubuntu 11.10. I tried some basic grep'ing but couldn't find a reference to "sched_getcpu" in either.</p> LTTng-modules - Feature #28 (Resolved): Implement the State Dumphttps://bugs.lttng.org/issues/282012-02-11T23:57:19ZAnonymous
<p>Re-implement LTTng 0.x 's statedump with the new toolchain.</p>
<p>This queries the state of each running process on the system at the start of a trace, and write it as a pseudo-event. This then allows the viewer to fill up its internal state system.</p>
<p>Tentatively aimed for 2.0, but it's not a blocker for the release.</p> LTTng-UST - Feature #25 (Resolved): Emit tracer environment metadatahttps://bugs.lttng.org/issues/252012-02-11T23:33:30ZAnonymous
<p>Same as issue <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Emit tracer environment metadata for the kernel (Resolved)" href="https://bugs.lttng.org/issues/21">#21</a> but for UST.</p> LTTng-tools - Feature #23 (Invalid): Implement trace log levelshttps://bugs.lttng.org/issues/232012-02-11T23:22:56ZAnonymous
<p>Also discuss the names and number of them.</p> LTTng-modules - Feature #21 (Resolved): Emit tracer environment metadata for the kernelhttps://bugs.lttng.org/issues/212012-02-11T23:17:43ZAnonymousBabeltrace - Feature #19 (Resolved): Make use tracer "environment" metadatahttps://bugs.lttng.org/issues/192012-02-11T22:44:52ZAnonymous
<p>Now tracers export "env" CTF metadata, so Babeltrace should interpret and print this accordingly.</p>