From: no-reply@lttng.org (bulu (LTTng Project))
Subject: [ltt-dev] [ltt-control] [bug] inside trace folder (/tmp/trace) all files are zero apart from kernel_0
Date: Wed, 13 Apr 2011 08:12:32 -0400 [thread overview]
Message-ID: <type=project&nid=234&host=@lttng.org> (raw)
Issue status update for
http://lttng.org/issue/234
Post a follow up:
http://lttng.org/comment/reply/234#comment-form
Project: ltt-control
Version: 0.88
Component: Code
Category: bug report
Priority: critical
Assigned to: admin
Status: needs review
Updated by: bulu
Hi, I am on mips.I am not able to get the kernel traces after following
procedure rightly.I have put the required patches. Cross-compiled the
lttctl and lttv.After doing lttctl -C -w /tmp/trace1 trace1, the trace
starts. Then I stop the trace by lttctl -D trace1. Here untill you press
"Cntrl+C" the trace1 does not stop.
And the output of lttv is like below.
lttv -m textDump -t /tmp/trace1
The input data file /var/tmp/trace1/metadata_0 does not contain a trace
The input data file /var/tmp/trace1/block_0 does not contain a trace
The input data file /var/tmp/trace1/fd_state_0 does not contain a trace
The input data file /var/tmp/trace1/fs_0 does not contain a trace
The input data file /var/tmp/trace1/global_state_0 does not contain a
trace
The input data file /var/tmp/trace1/input_0 does not contain a trace
The input data file /var/tmp/trace1/ipc_0 does not contain a trace
The input data file /var/tmp/trace1/irq_state_0 does not contain a trace
**
ERROR:tracefile.c:1365:map_block: assertion failed: (block_num <
tf->num_blocks)
/bin/lttv: line 15: 107 Aborted $0.real $*
And inside the /tmp/trace1 directory I am able to find the following
files doing
"ls -l"
-rwxr-xr-x 1 root root 0 Jan 1 00:04 block_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 fd_state_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 fs_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 global_state_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 input_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 ipc_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 irq_state_0
-rwxr-xr-x 1 root root 634880 Jan 1 00:04 kernel_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 metadata_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 mm_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 module_state_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 net_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 netif_state_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 rcu_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 softirq_state_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 task_state_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 userspace_0
-rwxr-xr-x 1 root root 0 Jan 1 00:04 vm_state_0
. All others are not having any data inside.
bulu
reply other threads:[~2011-04-13 12:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='type=project&nid=234&host=@lttng.org' \
--to=no-reply@lttng.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox