what happens to my ltt-statedump?

"yuanbor" <[email protected]>
Newsgroups gmane.linux.kernel.tracing
Message-ID <[email protected]>
from some document,I know that ltt-statedump can get following events:


--------------------------------------------------


Event: enumerate_file_descriptors
List of open file descriptors
name File name PID Process identifier fd File descriptor index in this process's task_struct
Event: enumerate_vm_maps
List of active vm maps
PID Process identifier start VM's start address end VM's end address flags VM area flags pgoff VM's page offset inode Inode associated with this VM
Event: enumerate_modules
List of loaded kernel modules
name Module name state Module's state ref Number of references to this module
Event: enumerate_interrupts
List of registered interrupts
name Interrupt name action action triggered by interrupt num Interrupt number
Event: enumerate_process_state
State of each process when statedump is performed
pid Process identifier parent_pid Parent process identifier name Process name mode Execution mode submode Execution submode status Process status
Event: statedump_end
Kernel state dump complete


--------------------------------------------------




so, I execute following cmd to get some traces


#-----------------------------------------------------
/sbin/modprobe ltt-control
/sbin/modprobe ltt-probe-core
/sbin/modprobe ltt-statedump

lttctl -n statedump -d -l /mnt/debugfs/ltt -t /tmp/trace

rm -f tmp/*
./file

lttctl -n statedump -R

/sbin/rmmod ltt-statedump
/sbin/rmmod ltt-probe-core
/sbin/rmmod ltt-control
#-----------------------------------------------------




but,after these cmd,when I run 'lttv -m textDump -t /tmp/trace',I just get these:


-------------------------------------------------------


** (process:2771): WARNING **: Facility checksum mismatch for facility core : kernel 0xB96B8A8D vs XML 0x1212DF53

Trace set contains 1 traces

core.state_dump_facility_load: 1827.685470503 (/home/yuanbor/trace/statedump/1184614014/control/facilities_0), 0, 0, UNNAMED, UNBRANDED, 0, 0x0, MODE_UNKNOWN { "core", 3110832781, 0, 4, 4, 4, 4, 4 }
End trace set

Traceset statistics:

statistics summed: 1
mode_types:
MODE_UNKNOWN:
submodes:
UNKNOWN:
event_types:
events count: 0
events:
mode_types:
event_types:
events count: 0
event_types:
events count: 0
processes:
unknown process:
cpu:
0:
functions:
0x0:
mode_types:
MODE_UNKNOWN:
submodes:
UNKNOWN:
event_types:
events count: 0
events:
mode_types:
event_types:
events count: 0
event_types:
events count: 0
mode_types:
MODE_UNKNOWN:
submodes:
UNKNOWN:
event_types:
events count: 0
events:
mode_types:
event_types:
events count: 0
event_types:
events count: 0
1:
functions:
0x0:
mode_types:
MODE_UNKNOWN:
submodes:
UNKNOWN:
event_types:
events count: 0
events:
mode_types:
event_types:
events count: 0
event_types:
events count: 0
mode_types:
MODE_UNKNOWN:
submodes:
UNKNOWN:
event_types:
events count: 0
events:
mode_types:
event_types:
events count: 0
event_types:
events count: 0
mode_types:
MODE_UNKNOWN:
submodes:
UNKNOWN:
event_types:
events count: 0
events:
mode_types:
event_types:
events count: 0
event_types:
events count: 0
statistics summed: 1
cpu:
0:
mode_types:
MODE_UNKNOWN:
submodes:
UNKNOWN:
event_types:
events count: 0
events:
mode_types:
event_types:
events count: 0
event_types:
events count: 0
1:
mode_types:
MODE_UNKNOWN:
submodes:
UNKNOWN:
event_types:
events count: 0
events:
mode_types:
event_types:
events count: 0
event_types:
events count: 0
mode_types:
MODE_UNKNOWN:
submodes:
UNKNOWN:
event_types:
events count: 0
events:
mode_types:
event_types:
events count: 0
event_types:
events count: 0




-------------------------------------------------------

_______________________________________________
Ltt-dev mailing list
[email protected]
http://listserv.shafik.org/mailman/listinfo/ltt-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.