From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] lttv: Segmentation fault while reading a trace
Date: Mon, 23 Mar 2009 11:03:00 -0400 [thread overview]
Message-ID: <20090323150300.GB18846@Krystal> (raw)
In-Reply-To: <a5fa0d9a0903230707j7ad17c37ia864903a9438b3b6@mail.gmail.com>
* VISHAL KANAUJIA (vishalkanaujia at gmail.com) wrote:
> Hi,
> I created trace with $ lttctl -C -w /tmp/trace1 trace1 and I did get
> acknowledgement that trace has been started. After stopping the
> trace I tried to read it. But I'm struck with following issue:
>
> [root at abc tmp]# lttv -m textDump -t /tmp/trace1
>
> ** (process:23164): CRITICAL **: cannot open trace /tmp/trace1
> /usr/local/bin/lttv: line 15: 23164 Segmentation fault $0.real $*
> [root at abc tmp]# ll !$
> ll /tmp/trace1
> total 520
> -rwxr-xr-x 1 root root 262144 2009-03-23 16:05 metadata_0
> -rwxr-xr-x 1 root root 262144 2009-03-23 16:05 metadata_1
>
You probably forgot to run
ltt-armall
before starting the trace.
Mathieu
> Am I missing something here?
>
> Thanks,
> Vishal
>
> PS: I have installed LTTng with following configuration:
>
> o $uname -a
> 2.6.29-rc3 #1 SMP Wed Mar 18 19:40:04 IST 2009 i686 i686 i386 GNU/Linux
> o LTTng path: patch-2.6.29-rc3-lttng-0.92
> o Linux Trace Toolkit Trace Control 0.65-11022009
> o Linux Trace Toolkit Visualizer 0.11.6-13112008
> _______________________________________________
> 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
prev parent reply other threads:[~2009-03-23 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 14:07 VISHAL KANAUJIA
2009-03-23 14:07 ` VISHAL KANAUJIA
2009-03-23 14:07 ` VISHAL KANAUJIA
2009-03-23 15:03 ` Mathieu Desnoyers [this message]
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=20090323150300.GB18846@Krystal \
--to=compudj@krystal.dyndns.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