Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: gausinghnsit@gmail.com (Gaurav Singh)
Subject: [ltt-dev] Trace extraction after Crash
Date: Tue, 10 Feb 2009 12:32:43 +0530	[thread overview]
Message-ID: <3cc7a0df0902092302p28b0339bp8e676773fb2c6f73@mail.gmail.com> (raw)

Hi everyone,

I was wondering if anyone has extracted the trace after a crash dump. The
following menuconfig option exists :

config LTT_VMCORE
        bool "Support trace extraction from crash dump"
        depends on LTT
        default y
        help
          If you enable this option, the Linux Trace Toolkit Tracer will
          support extacting ltt log from vmcore, which can be generated with
          kdump or LKCD tools.
          Special crash extension should be used to extract ltt buffers.

Now I understand it enables some code to enable extraction of trace from
crash dump. What are steps involved to get the trace after a crash ?

Regards
Gaurav
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20090210/c7b42dc1/attachment-0003.htm>


                 reply	other threads:[~2009-02-10  7:02 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=3cc7a0df0902092302p28b0339bp8e676773fb2c6f73@mail.gmail.com \
    --to=gausinghnsit@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