From: skrishnakar@gmail.com (srikanth krishnakar)
Subject: [ltt-dev] [URGENT]Re: Flight Recorder Testing on Linux-2.6.32
Date: Wed, 26 May 2010 12:30:27 +0530 [thread overview]
Message-ID: <AANLkTikB2DWpXqQSs9uip-eozq2s_t1lRksBktQ6O-zh@mail.gmail.com> (raw)
Message-ID: <20100526070027.axyjKYCRAAaxluPGaZmbBxJkY1DDqe-LCUAG_K9tEZc@z> (raw)
In-Reply-To: <AANLkTim7j9EhtFZ6qg4sp_jeCOMnFermiHNVvN0I6KGP@mail.gmail.com>
Hello Mathieu,
In the analysis of COREDUMP using *FLIGHT_RECORDER*, what are the steps I do
need to follow for tracing, because If i follow the steps :
1. Connect all markers (ltt-armall)
2. Start tracing (lttctl -Cw /tmp/trace1 trace1)
*Till here every thing is fine... w.r.t trace methods involved. Now say If
here I get KERNEL_PANIC, then what about my trace data that is still pending
and needs to be written to files.*
*I mean till I destroy the channels I will not get the trace data !! *
How do I resolve this situation !!! where kernel panics and no trace data
available for user ?
Any input are appreciated !!
Thanks,
Srikant
On Mon, May 24, 2010 at 6:59 PM, srikanth krishnakar
<skrishnakar at gmail.com>wrote:
> Hi Mathieu,
>
> I am trying to run through the LTTng Flight Recorder test on kernel
> Linux-2.6.32.13. Here are the steps I have followed :
>
>
> 1. Compiled the kernel Linux-2.6.32 + Lttng support
>
> 2. Booted the Lttng kernel
>
> 3. Loaded all the necessary modules, followed by :
>
> 4. Ran "ltt-armall"
>
> 5. Then started the tracing in flight recorder mode as:
>
> # lttctl -C -w /tmp/trace3 -o channel.all.overwrite=1 trace3
>
> 6. Then destroyed the channels, for write process to take place:
>
> # lttctl -D trace3
>
>
> Correct me If i am going wrong in any of the above steps, that are
> necessary for flight recorder testing.
>
> What is the difference do I find in normal LTTng tracing and the Flight
> Recorder mode ? What difference does the LTTV-GUI shows for LTTng Flight
> recorder mode ?
> (Is LKCD any way related to core dump tracing in Flight Recorder mode ?)
>
> Are there any additional steps required for carrying out the tracing in
> Flight recorder mode for CORE DUMP tracing.
>
> All the steps i have followed are from :
> http://lttng.org/cgi-bin/gitweb.cgi?p=lttv.git;a=blob_plain;f=LTTngManual.html#flight
>
> Any pointers would be appreciated !!
>
> Thanks in Advance !
>
> Regards
> Srikanth Krishnakar
> **********************
>
--
"The Good You Do, The Best You GET"
Regards
Srikanth Krishnakar
**********************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20100526/1ae4a26f/attachment.htm>
next prev parent reply other threads:[~2010-05-26 7:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 13:29 [ltt-dev] " srikanth krishnakar
2010-05-24 13:29 ` srikanth krishnakar
2010-05-24 13:29 ` srikanth krishnakar
2010-05-26 7:00 ` srikanth krishnakar [this message]
2010-05-26 7:00 ` [ltt-dev] [URGENT]Re: " srikanth krishnakar
2010-05-26 7:00 ` srikanth krishnakar
2010-05-26 13:24 ` Mathieu Desnoyers
2010-05-26 14:06 ` srikanth krishnakar
2010-05-26 14:06 ` srikanth krishnakar
2010-05-26 14:06 ` srikanth krishnakar
2010-05-26 15:14 ` Mathieu Desnoyers
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=AANLkTikB2DWpXqQSs9uip-eozq2s_t1lRksBktQ6O-zh@mail.gmail.com \
--to=skrishnakar@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