[lttng-dev] [PATCH] Improve lttng-tools lttng.c usage()

Mathieu Desnoyers compudj at krystal.dyndns.org
Wed Jan 25 14:19:34 EST 2012


* Thibault, Daniel (Daniel.Thibault at drdc-rddc.gc.ca) wrote:
>    This patch reorganises and augments the lttng-tools lttng.c usage() output in order to increase its legibility and usefulness.
> 
> ------------------------------
> From 003dd9e14a6e00754b11e4ea482f9bd3654d3b80 Wed, 25 Jan 2012 13:14:20 -0500
> From: Daniel U. Thibault <daniel.thibault at drdc-rddc.gc.ca>
> Date: Wed, 25 Jan 2012 13:14:00 -0500
> Subject: [PATCH] Improve lttng-tools lttng.c usage()
> 
> diff --git a/src/bin/lttng/lttng.c b/src/bin/lttng/lttng.c
> index aeaad14..0373839 100644
> --- a/src/bin/lttng/lttng.c
> +++ b/src/bin/lttng/lttng.c
> @@ -85,20 +85,21 @@
>  	fprintf(ofp, "usage: lttng [options] <command>\n");
>  	fprintf(ofp, "\n");
>  	fprintf(ofp, "Options:\n");
> -	fprintf(ofp, "  -h, --help             Show this help\n");
> -	fprintf(ofp, "  -g, --group NAME       Unix tracing group name. (default: tracing)\n");
> -	fprintf(ofp, "  -v, --verbose          Verbose mode\n");
> +	fprintf(ofp, "  -h, --help             Show this help and exit\n");

"and exit" -> useless to specify this in the help, implicit to showing
help.

> +	fprintf(ofp, "      --list-options     List the available lttng options and exit\n");
> +	fprintf(ofp, "      --list-commands    List the available lttng commands and exit\n");

--list* are only for bash completion. not sure it's useful to have them
at the top. "and exit" is useless here too imho.

> +	fprintf(ofp, "  -v, --verbose          Verbose mode (may be repeated up to 3 times\n");
> +	fprintf(ofp, "                         for increased verbosity)\n");

please give an example, e.g. "-vvv"

>  	fprintf(ofp, "  -q, --quiet            Quiet mode\n");
> +	fprintf(ofp, "  -g, --group NAME       Unix tracing group name. (default: tracing)\n");
>  	fprintf(ofp, "  -n, --no-sessiond      Don't spawn a session daemon\n");
> -	fprintf(ofp, "      --sessiond-path    Session daemon full path\n");
> -	fprintf(ofp, "      --list-options     Simple listing of lttng options\n");
> -	fprintf(ofp, "      --list-commands    Simple listing of lttng commands\n");
> +	fprintf(ofp, "  --sessiond-path PATH   Session daemon full path\n");

incorrect indentation of the help text.

>  	fprintf(ofp, "\n");
>  	fprintf(ofp, "Commands:\n");
> -	fprintf(ofp, "    add-context     Add context to event or/and channel\n");
> +	fprintf(ofp, "    add-context     Add context to event and/or channel\n");

yes.

>  	fprintf(ofp, "    calibrate       Quantify LTTng overhead\n");
>  	fprintf(ofp, "    create          Create tracing session\n");
> -	fprintf(ofp, "    destroy         Teardown tracing session\n");
> +	fprintf(ofp, "    destroy         Tear down tracing session\n");

yes.

>  	fprintf(ofp, "    enable-channel  Enable tracing channel\n");
>  	fprintf(ofp, "    enable-event    Enable tracing event\n");
>  	fprintf(ofp, "    disable-channel Disable tracing channel\n");
> @@ -109,7 +110,9 @@
>  	fprintf(ofp, "    stop            Stop tracing\n");
>  	fprintf(ofp, "    version         Show version information\n");
>  	fprintf(ofp, "\n");
> -	fprintf(ofp, "Please see the lttng(1) man page for full documentation.\n");
> +	fprintf(ofp, "Each command also has its own -h or --help option.\n");
> +	fprintf(ofp, "\n");
> +	fprintf(ofp, "Forthcoming: lttng(1) man page for full documentation.\n");

yes, very much needed.

Thanks,

Mathieu

>  	fprintf(ofp, "See http://lttng.org for updates, bug reports and news.\n");
>  }
> ------------------------------
> 
> Daniel U. Thibault
> R & D pour la défense Canada - Valcartier (RDDC Valcartier) / Defence R&D Canada - Valcartier (DRDC Valcartier)
> Système de systèmes (SdS) / System of Systems (SoS)
> Solutions informatiques et expérimentations (SIE) / Computing Solutions and Experimentations (CSE)
> 2459 Boul. Pie XI Nord
> Québec, QC  G3J 1X5
> CANADA
> Vox : (418) 844-4000 x4245
> Fax : (418) 844-4538
> [Secteur-SI]\\sds-dut-opti980, \\edge
> NAC: 918V QSDJ
> Gouvernement du Canada / Government of Canada
> <http://www.valcartier.drdc-rddc.gc.ca/>
> 
> 
> -----Message d'origine-----
> De : lttng-dev-request at lists.lttng.org [mailto:lttng-dev-request at lists.lttng.org] 
> Envoyé : 25 janvier 2012 11:07
> À : lttng-dev at lists.lttng.org
> Objet : lttng-dev Digest, Vol 45, Issue 38
> 
> Send lttng-dev mailing list submissions to
> 	lttng-dev at lists.lttng.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> or, via email, send a message with subject or body 'help' to
> 	lttng-dev-request at lists.lttng.org
> 
> You can reach the person managing the list at
> 	lttng-dev-owner at lists.lttng.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lttng-dev digest..."
> 
> 
> Today's Topics:
> 
>    1. [BUG] lttng-tools linking with GNU gold (Mathieu Desnoyers)
>    2. Errors using lttng-modules v2.0-pre11 (Bernd Hufmann)
>    3. Re: lttng create freezes sometimes (Mathieu Desnoyers)
>    4. Re: traces omissions (Mathieu Desnoyers)
>    5. Re: Errors using lttng-modules v2.0-pre11 (Mathieu Desnoyers)
>    6. Re: Errors using lttng-modules v2.0-pre11 (Bernd Hufmann)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 24 Jan 2012 19:38:36 -0500
> From: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
> To: dgoulet at efficios.com
> Cc: lttng-dev at lists.lttng.org
> Subject: [lttng-dev] [BUG] lttng-tools linking with GNU gold
> Message-ID: <20120125003836.GB23314 at Krystal>
> Content-Type: text/plain; charset=us-ascii
> 
> Hi David,
> 
> With commit bbccc3d2cb9f83aecf00a207de9eef68c766bf9c of lttng-tools,
> linking consumerd and sessiond now fails on my machine that uses GNU
> gold as linker with:
> 
>   CCLD   lttng-consumerd
> /usr/bin/ld: internal error in relocate_tls, at
> ../../gold/x86_64.cc:3187
> collect2: ld returned 1 exit status
> make[3]: *** [lttng-consumerd] Error 1
> 
> I suspect the recent refactoring turned some dynamically linked
> libraries into statically linked ones, which might trigger this issue.
> Also, added dependencies on liburcu might trigger this issue, given that
> liburcu has TLS data.
> 
> Investigation will be needed though,
> 
> Thanks,
> 
> Mathieu
> 
> -- 
> Mathieu Desnoyers
> Operating System Efficiency R&D Consultant
> EfficiOS Inc.
> http://www.efficios.com
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Wed, 25 Jan 2012 09:39:57 -0500
> From: Bernd Hufmann <Bernd.Hufmann at ericsson.com>
> To: "lttng-dev at lists.lttng.org" <lttng-dev at lists.lttng.org>
> Subject: [lttng-dev] Errors using lttng-modules v2.0-pre11
> Message-ID: <4F20143D.2080408 at ericsson.com>
> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
> 
> Hello
> 
> I installed the lttng-modules v2.0-pre11 from source code (git 
> repository). The installation went without problems. But I'm getting the 
> errors below when executing "sudo lttng list -k".
> I'm running Ubuntu with a kernel 3.04. lttng-tools version is v2.0-pre18.
> 
> Could someone please look into this problem and let me know how I can 
> overcome this issue?
> 
> BTW, before installing lttng-modules v2.0-pre11, I tried to upgrade to 
> the latest in master from an older version.
> 
> Best Regards
> Bernd
> 
> WARNING: Error inserting lttng_ftrace 
> (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> WARNING: Error inserting lttng_kprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> WARNING: Error inserting lttng_kretprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module format
> FATAL: Error inserting ltt_relay 
> (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> WARNING: Error inserting lttng_ftrace 
> (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> WARNING: Error inserting lttng_kprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> WARNING: Error inserting lttng_kretprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module format
> WARNING: Error inserting ltt_relay 
> (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> FATAL: Error inserting ltt_ring_buffer_client_discard 
> (/lib/modules/3.0.4/extra/ltt-ring-buffer-client-discard.ko): Invalid 
> module format
> WARNING: Error inserting lttng_ftrace 
> (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> WARNING: Error inserting lttng_kprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> WARNING: Error inserting lttng_kretprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module format
> WARNING: Error inserting ltt_relay 
> (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> FATAL: Error inserting ltt_ring_buffer_client_overwrite 
> (/lib/modules/3.0.4/extra/ltt-ring-buffer-client-overwrite.ko): Invalid 
> module format
> WARNING: Error inserting lttng_ftrace 
> (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> WARNING: Error inserting lttng_kprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> WARNING: Error inserting lttng_kretprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module format
> WARNING: Error inserting ltt_relay 
> (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> FATAL: Error inserting ltt_ring_buffer_metadata_client 
> (/lib/modules/3.0.4/extra/ltt-ring-buffer-metadata-client.ko): Invalid 
> module format
> WARNING: Error inserting lttng_ftrace 
> (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> WARNING: Error inserting lttng_kprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> WARNING: Error inserting lttng_kretprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module format
> WARNING: Error inserting ltt_relay 
> (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> FATAL: Error inserting ltt_ring_buffer_client_mmap_discard 
> (/lib/modules/3.0.4/extra/ltt-ring-buffer-client-mmap-discard.ko): 
> Invalid module format
> WARNING: Error inserting lttng_ftrace 
> (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> WARNING: Error inserting lttng_kprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> WARNING: Error inserting lttng_kretprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module format
> WARNING: Error inserting ltt_relay 
> (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> FATAL: Error inserting ltt_ring_buffer_client_mmap_overwrite 
> (/lib/modules/3.0.4/extra/ltt-ring-buffer-client-mmap-overwrite.ko): 
> Invalid module format
> WARNING: Error inserting lttng_ftrace 
> (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> WARNING: Error inserting lttng_kprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> WARNING: Error inserting lttng_kretprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module format
> WARNING: Error inserting ltt_relay 
> (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> FATAL: Error inserting ltt_ring_buffer_metadata_mmap_client 
> (/lib/modules/3.0.4/extra/ltt-ring-buffer-metadata-mmap-client.ko): 
> Invalid module format
> WARNING: Error inserting lttng_ftrace 
> (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> WARNING: Error inserting lttng_kprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> WARNING: Error inserting lttng_kretprobes 
> (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module format
> WARNING: Error inserting ltt_relay 
> (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> FATAL: Error inserting lttng_probe_lttng 
> (/lib/modules/3.0.4/extra/probes/lttng-probe-lttng.ko): Invalid module 
> format
> FATAL: Error inserting lttng_probe_block 
> (/lib/modules/3.0.4/extra/probes/lttng-probe-block.ko): Invalid module 
> format
> FATAL: Error inserting lttng_probe_irq 
> (/lib/modules/3.0.4/extra/probes/lttng-probe-irq.ko): Invalid module format
> FATAL: Error inserting lttng_probe_kvm 
> (/lib/modules/3.0.4/extra/probes/lttng-probe-kvm.ko): Invalid module format
> FATAL: Error inserting lttng_probe_sched 
> (/lib/modules/3.0.4/extra/probes/lttng-probe-sched.ko): Invalid module 
> format
> Error: Unable to list kernel events
> Error: Kernel tracer not available
> 
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Wed, 25 Jan 2012 09:41:57 -0500
> From: Mathieu Desnoyers <compudj at krystal.dyndns.org>
> To: S?bastien Barth?l?my <barthelemy at crans.org>
> Cc: lttng-dev at lists.lttng.org, dgoulet at efficios.com
> Subject: Re: [lttng-dev] lttng create freezes sometimes
> Message-ID: <20120125144157.GA3754 at Krystal>
> Content-Type: text/plain; charset=iso-8859-1
> 
> Hi S?bastien,
> 
> * S?bastien Barth?l?my (barthelemy at crans.org) wrote:
> > Hello David,
> > 
> > I just tried with lttng-tools 2.0-pre17 and still have the problem.
> 
> Please try with commit:
> 
> commit 5a532b6873b6d619381c0188b91e48106e639808
> Author: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
> Date:   Wed Jan 25 09:39:28 2012 -0500
> 
>     Fix lttng sessiond spawn wait race
>     
>     If the child is scheduled before the parent, using "pause()" in the
>     parent could be executed after the signal has been handled: that's
>     entirely racy. Use a proper signal handler and flag to handle this
>     racelessly.
>     
>     Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
> 
> Let me know how it works,
> 
> Best regards,
> 
> Mathieu
> 
> > 
> > -- Cheers
> > S?bastien
> > 
> > _______________________________________________
> > lttng-dev mailing list
> > lttng-dev at lists.lttng.org
> > http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> > 
> 
> -- 
> Mathieu Desnoyers
> Operating System Efficiency R&D Consultant
> EfficiOS Inc.
> http://www.efficios.com
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Wed, 25 Jan 2012 09:43:57 -0500
> From: Mathieu Desnoyers <compudj at krystal.dyndns.org>
> To: S?bastien Barth?l?my <barthelemy at crans.org>
> Cc: lttng-dev at lists.lttng.org
> Subject: Re: [lttng-dev] traces omissions
> Message-ID: <20120125144357.GB3754 at Krystal>
> Content-Type: text/plain; charset=iso-8859-1
> 
> * S?bastien Barth?l?my (barthelemy at crans.org) wrote:
> > Hello all,
> > 
> > I have yet another difficulty using LTTng.
> > 
> > I run a program which dlopens a module (called DCM) which is
> > instrumented with ust (provider == qi_dcm), and which calls functions
> > from a processsyncclient library (PSC for short), also instrumented
> > with ust (provider == qi_bn_ipc_psc).
> > 
> > When I run the program, I ld_preload the two probes provider as in
> > 
> > LD_PRELOAD="$PREFIX/lib/libtp_processsyncclient_pipe.so
> > $PREFIX/lib/libtp_dcm.so" LD_LIBRARY_PATH=$PREFIX/lib
> > $PREFIX/bin/naoqi-bin &
> > 
> > This used to work, but when I run it now, I only get traces from the
> > processsyncclient probes, not from the DCM ones. However, they are
> > triggered by the same code paths, so I expect to get events from both
> > of them.
> > 
> > I checked that the probes are correctly registered:
> > 
> > libust[3739/3739]: just registered probe qi_dcm containing 2 events
> > (in ltt_probe_register() at ltt-probes.c:109)
> > libust[3739/3739]: just registered probe qi_bn_ipc_psc containing 3
> > events (in ltt_probe_register() at ltt-probes.c:109)
> > 
> > and that I have symbols from both of them in the DCM module (so it not
> > a simple #define error):
> > 
> > $ nm libdcm_hal.so |grep _qi_
> > 0005cab4 r _ZL26__tp_strtab_qi_dcm___state
> > 0006c22c d _ZL31__tracepoint_ptr_qi_dcm___state
> > 0005cad8 r _ZL35__tp_strtab_qi_bn_ipc_psc___waiting
> > 0005cac1 r _ZL35__tp_strtab_qi_dcm___clock_realtime
> > 0005cb0f r _ZL38__tp_strtab_qi_bn_ipc_psc___notify_end
> > 0006c234 d _ZL40__tracepoint_ptr_qi_bn_ipc_psc___waiting
> > 0006c230 d _ZL40__tracepoint_ptr_qi_dcm___clock_realtime
> > 0006c23c d _ZL43__tracepoint_ptr_qi_bn_ipc_psc___notify_end
> > 0005caf0 r _ZL44__tp_strtab_qi_bn_ipc_psc___finished_waiting
> > 0006c238 d _ZL49__tracepoint_ptr_qi_bn_ipc_psc___finished_waiting
> > 00040566 t __tracepoint_cb_qi_dcm___clock_realtime
> > 000404c7 t __tracepoint_cb_qi_dcm___state
> > 0006c214 D __tracepoint_qi_bn_ipc_psc___finished_waiting
> > 0006c220 D __tracepoint_qi_bn_ipc_psc___notify_end
> > 0006c208 D __tracepoint_qi_bn_ipc_psc___waiting
> > 0006c1fc D __tracepoint_qi_dcm___clock_realtime
> > 0006c1f0 D __tracepoint_qi_dcm___state
> > 
> > 
> > I also get these messages (not sure what they mean):
> > 
> > liblttng_ust_tracepoint[3739/3739]: just registered a tracepoints
> > section from 0xb1fa1860 and having 1 tracepoints (in
> > tracepoint_register_lib() at tracepoint.c:610)
> > liblttng_ust_tracepoint[3739/3739]: just registered a tracepoints
> > section from 0xb203822c and having 5 tracepoints (in
> > tracepoint_register_lib() at tracepoint.c:610)
> > liblttng_ust_tracepoint[3739/3739]: just registered a tracepoints
> > section from 0xb04b06f4 and having 2 tracepoints (in
> > tracepoint_register_lib() at tracepoint.c:610)
> > 
> > Is this use case expected?
> > 
> > I fear I'm running out of ideas, how could investigate the matter further?
> 
> This rather sounds like an event name typo in create-event. Can you
> provide the exact list of lttng commands you used ?
> 
> Thanks,
> 
> Mathieu
> 
> > 
> > _______________________________________________
> > lttng-dev mailing list
> > lttng-dev at lists.lttng.org
> > http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> > 
> 
> -- 
> Mathieu Desnoyers
> Operating System Efficiency R&D Consultant
> EfficiOS Inc.
> http://www.efficios.com
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Wed, 25 Jan 2012 10:30:21 -0500
> From: Mathieu Desnoyers <compudj at krystal.dyndns.org>
> To: Bernd Hufmann <Bernd.Hufmann at ericsson.com>
> Cc: "lttng-dev at lists.lttng.org" <lttng-dev at lists.lttng.org>
> Subject: Re: [lttng-dev] Errors using lttng-modules v2.0-pre11
> Message-ID: <20120125153021.GA10959 at Krystal>
> Content-Type: text/plain; charset=us-ascii
> 
> * Bernd Hufmann (Bernd.Hufmann at ericsson.com) wrote:
> > Hello
> >
> > I installed the lttng-modules v2.0-pre11 from source code (git  
> > repository). The installation went without problems. But I'm getting the  
> > errors below when executing "sudo lttng list -k".
> > I'm running Ubuntu with a kernel 3.04. lttng-tools version is v2.0-pre18.
> >
> > Could someone please look into this problem and let me know how I can  
> > overcome this issue?
> >
> > BTW, before installing lttng-modules v2.0-pre11, I tried to upgrade to  
> > the latest in master from an older version.
> 
> Please try to remove all lttng modules from your
> /lib/modules/3.0.4/extra directory, go to your lttng modules tree, make
> clean, make, and, as root, make modules_install.
> 
> This should fix it. I expect that currently your modules are built
> against the wrong kernel tree.
> 
> If it does not fix it, investigate whether your /lib/modules/3.0.4/build
> symlink points to a kernel tree (or kernel headers) that match your
> running kernel.
> 
> Best regards,
> 
> Mathieu
> 
> >
> > Best Regards
> > Bernd
> >
> > WARNING: Error inserting lttng_ftrace  
> > (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> > WARNING: Error inserting lttng_kprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> > WARNING: Error inserting lttng_kretprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module 
> > format
> > FATAL: Error inserting ltt_relay  
> > (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> > WARNING: Error inserting lttng_ftrace  
> > (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> > WARNING: Error inserting lttng_kprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> > WARNING: Error inserting lttng_kretprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module 
> > format
> > WARNING: Error inserting ltt_relay  
> > (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> > FATAL: Error inserting ltt_ring_buffer_client_discard  
> > (/lib/modules/3.0.4/extra/ltt-ring-buffer-client-discard.ko): Invalid  
> > module format
> > WARNING: Error inserting lttng_ftrace  
> > (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> > WARNING: Error inserting lttng_kprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> > WARNING: Error inserting lttng_kretprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module 
> > format
> > WARNING: Error inserting ltt_relay  
> > (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> > FATAL: Error inserting ltt_ring_buffer_client_overwrite  
> > (/lib/modules/3.0.4/extra/ltt-ring-buffer-client-overwrite.ko): Invalid  
> > module format
> > WARNING: Error inserting lttng_ftrace  
> > (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> > WARNING: Error inserting lttng_kprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> > WARNING: Error inserting lttng_kretprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module 
> > format
> > WARNING: Error inserting ltt_relay  
> > (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> > FATAL: Error inserting ltt_ring_buffer_metadata_client  
> > (/lib/modules/3.0.4/extra/ltt-ring-buffer-metadata-client.ko): Invalid  
> > module format
> > WARNING: Error inserting lttng_ftrace  
> > (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> > WARNING: Error inserting lttng_kprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> > WARNING: Error inserting lttng_kretprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module 
> > format
> > WARNING: Error inserting ltt_relay  
> > (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> > FATAL: Error inserting ltt_ring_buffer_client_mmap_discard  
> > (/lib/modules/3.0.4/extra/ltt-ring-buffer-client-mmap-discard.ko):  
> > Invalid module format
> > WARNING: Error inserting lttng_ftrace  
> > (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> > WARNING: Error inserting lttng_kprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> > WARNING: Error inserting lttng_kretprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module 
> > format
> > WARNING: Error inserting ltt_relay  
> > (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> > FATAL: Error inserting ltt_ring_buffer_client_mmap_overwrite  
> > (/lib/modules/3.0.4/extra/ltt-ring-buffer-client-mmap-overwrite.ko):  
> > Invalid module format
> > WARNING: Error inserting lttng_ftrace  
> > (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> > WARNING: Error inserting lttng_kprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> > WARNING: Error inserting lttng_kretprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module 
> > format
> > WARNING: Error inserting ltt_relay  
> > (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> > FATAL: Error inserting ltt_ring_buffer_metadata_mmap_client  
> > (/lib/modules/3.0.4/extra/ltt-ring-buffer-metadata-mmap-client.ko):  
> > Invalid module format
> > WARNING: Error inserting lttng_ftrace  
> > (/lib/modules/3.0.4/extra/probes/lttng-ftrace.ko): Invalid module format
> > WARNING: Error inserting lttng_kprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kprobes.ko): Invalid module format
> > WARNING: Error inserting lttng_kretprobes  
> > (/lib/modules/3.0.4/extra/probes/lttng-kretprobes.ko): Invalid module 
> > format
> > WARNING: Error inserting ltt_relay  
> > (/lib/modules/3.0.4/extra/ltt-relay.ko): Invalid module format
> > FATAL: Error inserting lttng_probe_lttng  
> > (/lib/modules/3.0.4/extra/probes/lttng-probe-lttng.ko): Invalid module  
> > format
> > FATAL: Error inserting lttng_probe_block  
> > (/lib/modules/3.0.4/extra/probes/lttng-probe-block.ko): Invalid module  
> > format
> > FATAL: Error inserting lttng_probe_irq  
> > (/lib/modules/3.0.4/extra/probes/lttng-probe-irq.ko): Invalid module 
> > format
> > FATAL: Error inserting lttng_probe_kvm  
> > (/lib/modules/3.0.4/extra/probes/lttng-probe-kvm.ko): Invalid module 
> > format
> > FATAL: Error inserting lttng_probe_sched  
> > (/lib/modules/3.0.4/extra/probes/lttng-probe-sched.ko): Invalid module  
> > format
> > Error: Unable to list kernel events
> > Error: Kernel tracer not available
> >
> >
> > _______________________________________________
> > lttng-dev mailing list
> > lttng-dev at lists.lttng.org
> > http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> >
> 
> -- 
> Mathieu Desnoyers
> Operating System Efficiency R&D Consultant
> EfficiOS Inc.
> http://www.efficios.com
> 
> 
> 
> 
> 
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> 

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com



More information about the lttng-dev mailing list