[ltt-dev] No marker of name kernel_arch_syscall_entry found

[Mathieu Desnoyers]

Did you run the ltt-armall script before starting lttctl ? Please review
the updated "quickstart guide" to make sure you did everything right.

Mathieu

* Stefano Babic (stefano.babic at babic.homelinux.org) wrote:
> Hi all,
> 
> I applied lttng 0.10.0-pre52 on kernel 2.6.25 for an embedded system
> based on powerpc. In the past I had lttng 0.9.10 and kernel 2.6.22.
> 
> I can apply all patches to the kernel and the target seems working
> flawless. I can start collecting traces with ltt-ctl (I tried version
> 0.44 and version 0.48) and I get traces in the directory I set.
> 
> However, lttv does not display the traces. I tried
> lttv-0.10.0-pre13-27052008, but it crashes as follows:
> 
> ** (process:31869): WARNING **: parse_trace_header error
> ** (process:31869): WARNING **: parse_trace_header error
> ** (process:31869): WARNING **: No marker of name
> kernel_arch_syscall_entry found
> (process:31869): GLib-CRITICAL **: g_array_remove_range: assertion
> `index_ < array->len' failed
> ** (process:31869): WARNING **: No marker of name kernel_arch_trap_entry
> found
> bin/lttv: line 15: 31869 Segmentation fault      $0.real $*
> 
> 
> 
> I downloaded the last version from the svn repository. This does not
> crash, but it reports that it founds no markers:
> 
> ** (lttv.real:19934): WARNING **: No marker of name list_statedump_end found
> ** (lttv.real:19934): WARNING **: No marker of name
> kernel_sched_schedule found
> ** (lttv.real:19934): WARNING **: No marker of name kernel_process_fork
> found
> ** (lttv.real:19934): WARNING **: No marker of name kernel_process_exit
> found
> ** (lttv.real:19934): WARNING **: No marker of name fs_exec found
> .....
> 
> Only the events core_marker_id and core_marker_format are displayed. No
> process is shown in the traces.
> 
> I see no problem during kernel compilation and in Module.markers I see
> the markers that lttv does not find, for example:
> 
> kernel_process_fork     vmlinux parent_pid %d child_pid %d child_tgid %d
> 
> Which could be the reason lttv does not find the markers ?
> 
> I have see a different behavior between lttctl-0.44 and lttctl-0.48,too.
> The former version generates xml files in the eventdef directory for all
> facilities :
> 
> -bash-3.2# lttctl -n trace -d -l /mnt/debugfs/ltt -t /tmp/trace
> Linux Trace Toolltt_control : trace trace
> kit Trace Control 0.44-21092007
> 
> Controlling trace : trace
> Linux Trace Toolkit Trace Daemon 0.44-21092007
> Reading from debugfs directory : /mnt/debugfs/ltt/trace
> Writing to trace directory : /tmp/trace
> 
> Creating supplementary trace files
> Appending facility file core.xml
> Appending facility file fs.xml
> Appending facility file kernel.xml
> Appending facility file kernel_arch_arm.xml
> ....
> 
> Version 0.48 does not generate the eventdef at all. Is this the correct
> behavior ? Or probably is something wrong on my system ?
> 
> Kind regards,
> Stefano
> 
> -- 
> stefano <stefano.babic at babic.homelinux.org>
> GPG Key: 0x55814DDE
> Fingerprint 4E85 2A66 4CBA 497A 2A7B D3BF 5973 F216 5581 4DDE
> 
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68