Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: sr.muralidhar@gmail.com (Murali S R)
Subject: [ltt-dev] [Lttng] Need help in running the Lttng on ARMv7 hardware with linux 2.6.35.7 kernel
Date: Thu, 28 Apr 2011 15:38:49 +0530	[thread overview]
Message-ID: <BANLkTikRO_eCLR09iJv7FqmTp6y_tUY83A@mail.gmail.com> (raw)

Hi All,

I am trying to run lttng on ARMv7 target with the following
Kernel --- linux 2.6.35.7 kernel and
Lttng Kernel Patch --- patch-2.6.35.7-lttng-0.232.tar.bz2
Modules --- lttng-modules-0.19.1.tar.bz2
Control Modules --- ltt-control-0.88-09242010.tar.gz

Whenever i enable the statedump ( by loading the ltt-statedump module) and
run lttctl tracing ( lttctl -C -w /tmp/trace trace ),
immediately a log "LTT Statedump end" is thrown.

After which i can still see some trace data being accumulated in the trace
path (/tmp/trace).

Now if i close the tracing (lttctl -D trace) & try to view the trace using
lttv-gui, It gets terminated with segmentation fault error.

Can anyone help in letting me know where i am doing wrong.
Also, is there any means to trace only a particular module instead of entire
kernel.

Thanks in advance :)

-- 
Regards,
Murali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20110428/f1a64dac/attachment-0003.htm>


WARNING: multiple messages have this Message-ID
From: sr.muralidhar@gmail.com (Murali S R)
Subject: [ltt-dev] [Lttng] Need help in running the Lttng on ARMv7 hardware with linux 2.6.35.7 kernel
Date: Thu, 28 Apr 2011 15:38:49 +0530	[thread overview]
Message-ID: <BANLkTikRO_eCLR09iJv7FqmTp6y_tUY83A@mail.gmail.com> (raw)
Message-ID: <20110428100849.VrBeNW7Q-n15SUj1HXZoMAwif_Q4-e7I2mwxKo3Lo4A@z> (raw)

Hi All,

I am trying to run lttng on ARMv7 target with the following
Kernel --- linux 2.6.35.7 kernel and
Lttng Kernel Patch --- patch-2.6.35.7-lttng-0.232.tar.bz2
Modules --- lttng-modules-0.19.1.tar.bz2
Control Modules --- ltt-control-0.88-09242010.tar.gz

Whenever i enable the statedump ( by loading the ltt-statedump module) and
run lttctl tracing ( lttctl -C -w /tmp/trace trace ),
immediately a log "LTT Statedump end" is thrown.

After which i can still see some trace data being accumulated in the trace
path (/tmp/trace).

Now if i close the tracing (lttctl -D trace) & try to view the trace using
lttv-gui, It gets terminated with segmentation fault error.

Can anyone help in letting me know where i am doing wrong.
Also, is there any means to trace only a particular module instead of entire
kernel.

Thanks in advance :)

-- 
Regards,
Murali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20110428/f1a64dac/attachment-0002.htm>


WARNING: multiple messages have this Message-ID
From: sr.muralidhar@gmail.com (Murali S R)
Subject: [ltt-dev] [Lttng] Need help in running the Lttng on ARMv7 hardware with linux 2.6.35.7 kernel
Date: Thu, 28 Apr 2011 15:38:49 +0530	[thread overview]
Message-ID: <BANLkTikRO_eCLR09iJv7FqmTp6y_tUY83A@mail.gmail.com> (raw)
Message-ID: <20110428100849.Kk82fA2GAgOOY7fQ2Z806R3khp1LT85mJSwecTQAksg@z> (raw)

Hi All,

I am trying to run lttng on ARMv7 target with the following
Kernel --- linux 2.6.35.7 kernel and
Lttng Kernel Patch --- patch-2.6.35.7-lttng-0.232.tar.bz2
Modules --- lttng-modules-0.19.1.tar.bz2
Control Modules --- ltt-control-0.88-09242010.tar.gz

Whenever i enable the statedump ( by loading the ltt-statedump module) and
run lttctl tracing ( lttctl -C -w /tmp/trace trace ),
immediately a log "LTT Statedump end" is thrown.

After which i can still see some trace data being accumulated in the trace
path (/tmp/trace).

Now if i close the tracing (lttctl -D trace) & try to view the trace using
lttv-gui, It gets terminated with segmentation fault error.

Can anyone help in letting me know where i am doing wrong.
Also, is there any means to trace only a particular module instead of entire
kernel.

Thanks in advance :)

-- 
Regards,
Murali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20110428/f1a64dac/attachment.htm>


             reply	other threads:[~2011-04-28 10:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28 10:08 Murali S R [this message]
2011-04-28 10:08 ` Murali S R
2011-04-28 10:08 ` Murali S R
2011-04-28 12:31 ` Mathieu Desnoyers
     [not found] ` <BLU0-SMTP843EAF9BC8918EA1C2AD10969B0@phx.gbl>
2011-04-28 16:04   ` Murali S R
2011-04-28 16:04     ` Murali S R
2011-04-28 16:04     ` Murali S R
2011-04-28 16:45     ` Mathieu Desnoyers
     [not found]     ` <BLU0-SMTP46743BFC767121197A11B2969B0@phx.gbl>
2011-04-29  6:49       ` Murali S R
2011-04-29  6:49         ` Murali S R
2011-04-29  6:49         ` Murali S R

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=BANLkTikRO_eCLR09iJv7FqmTp6y_tUY83A@mail.gmail.com \
    --to=sr.muralidhar@gmail.com \
    /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