Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: minyard@acm.org (Corey Minyard)
Subject: [lttng-dev] Extract lttng trace from kernel coredump
Date: Tue, 18 Feb 2014 13:29:23 -0600	[thread overview]
Message-ID: <5303B493.7080200@acm.org> (raw)
In-Reply-To: <353610105.9520.1390071650232.JavaMail.zimbra@efficios.com>

I have attached some gdb macros for dumping LTT buffers from a kernel
coredump.  I haven't done a lot of testing, though.

I do have one question.  I've been getting the metadata by taking a
snapshot right when the trace starts and saving that to stick into the
trace output from the coredump.  Is that the best way, or is there some
other way I can extract it?  There doesn't seem to be a metadata channel
running in snapshot mode.

Thanks,

-corey
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ltt.py
Type: text/x-python
Size: 16072 bytes
Desc: not available
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20140218/00922103/attachment.py>


  parent reply	other threads:[~2014-02-18 19:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52D46B33.4010401@acm.org>
     [not found] ` <20140114184243.GC8177@thessa>
     [not found]   ` <52D5A08F.4020204@acm.org>
     [not found]     ` <1303248645.9400.1390063653581.JavaMail.zimbra@efficios.com>
     [not found]       ` <52DAC820.7000005@acm.org>
     [not found]         ` <353610105.9520.1390071650232.JavaMail.zimbra@efficios.com>
2014-02-13 19:31           ` Corey Minyard
2014-02-18 20:02             ` Mathieu Desnoyers
2014-02-19 18:52               ` Corey Minyard
2014-02-18 19:29           ` Corey Minyard [this message]
2014-02-18 21:02             ` Mathieu Desnoyers
2014-02-18 21:36               ` Corey Minyard
2014-02-18 21:42               ` Mathieu Desnoyers
2014-02-18 21:59                 ` 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=5303B493.7080200@acm.org \
    --to=minyard@acm.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