From: muvarov@gmail.com (Maxim Uvarov)
Subject: [ltt-dev] ltt buffers from kernel memory dump extractor
Date: Thu, 19 Aug 2010 20:53:50 +0400 [thread overview]
Message-ID: <AANLkTik6a-TCO1+tqp-ap-iGE8hYKp0ntBk-iDRKPjQx@mail.gmail.com> (raw)
Hello,
There is a tool to extract LTT buffers from kernel dump. The general
propose of it is to have flight recorder on linux box.
So that you can run LTT in overwrite mode to keep track about all
system or program events in cycling buffer. When you will get kernel
panic it will be possible to analyze which events were in the system
before crash.
I tried to write it with minimal requirements to external
applications. The latest gdb has so named python macro. So this is
only one single requirement.
Tar ball with sources is attached.
How to use:
1. Compile kernel with:
- kdump support - refer to Documentation/kdump documentation.
- ltt with CONFIG_LTT_VMCORE option.
- debug info is needed to read information from kernel dump.
2. Run LTT in flight recorder mode with -o channel.all.overwrite=1 option.
lttctl -C -w /root/trace1 trace1 -o channel.all.overwrite=1
ltt-armall
3. Get kernel dump from /proc/vmcore and place it in directory with
ltt.py and .gdbinit.
4. Compile helper function, run make.
5. Get buffers from vmcore and save that to file:
gdb vmlinux vmcore
> lttsavebuffers
Directory with trace name will appear (trace1).
6. Apply lttvmcore.patch patch to ltt viewer lttvmcore.patch
7. Show trace:
lttv -m textDump -t ./trace1
--
Best regards,
Maxim Uvarov
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lttvmcoreV01.tar.gz
Type: application/x-gzip
Size: 12090 bytes
Desc: not available
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20100819/c54603b4/attachment.bin>
WARNING: multiple messages have this Message-ID
From: muvarov@gmail.com (Maxim Uvarov)
Subject: [ltt-dev] ltt buffers from kernel memory dump extractor
Date: Thu, 19 Aug 2010 20:53:50 +0400 [thread overview]
Message-ID: <AANLkTik6a-TCO1+tqp-ap-iGE8hYKp0ntBk-iDRKPjQx@mail.gmail.com> (raw)
Message-ID: <20100819165350.YPrqk3vXSsARZuLbH52j15oLsrWKqWRyTYf2bSDIJqk@z> (raw)
Hello,
There is a tool to extract LTT buffers from kernel dump. The general
propose of it is to have flight recorder on linux box.
So that you can run LTT in overwrite mode to keep track about all
system or program events in cycling buffer. When you will get kernel
panic it will be possible to analyze which events were in the system
before crash.
I tried to write it with minimal requirements to external
applications. The latest gdb has so named python macro. So this is
only one single requirement.
Tar ball with sources is attached.
How to use:
1. Compile kernel with:
- kdump support - refer to Documentation/kdump documentation.
- ltt with CONFIG_LTT_VMCORE option.
- debug info is needed to read information from kernel dump.
2. Run LTT in flight recorder mode with -o channel.all.overwrite=1 option.
lttctl -C -w /root/trace1 trace1 -o channel.all.overwrite=1
ltt-armall
3. Get kernel dump from /proc/vmcore and place it in directory with
ltt.py and .gdbinit.
4. Compile helper function, run make.
5. Get buffers from vmcore and save that to file:
gdb vmlinux vmcore
> lttsavebuffers
Directory with trace name will appear (trace1).
6. Apply lttvmcore.patch patch to ltt viewer lttvmcore.patch
7. Show trace:
lttv -m textDump -t ./trace1
--
Best regards,
Maxim Uvarov
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lttvmcoreV01.tar.gz
Type: application/x-gzip
Size: 12090 bytes
Desc: not available
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100819/c54603b4/attachment-0002.bin>
WARNING: multiple messages have this Message-ID
From: muvarov@gmail.com (Maxim Uvarov)
Subject: [ltt-dev] ltt buffers from kernel memory dump extractor
Date: Thu, 19 Aug 2010 20:53:50 +0400 [thread overview]
Message-ID: <AANLkTik6a-TCO1+tqp-ap-iGE8hYKp0ntBk-iDRKPjQx@mail.gmail.com> (raw)
Message-ID: <20100819165350.Id_Za9kbYjBIMPOLVY5fXHp2bnPcjR35KUmFSQRCggQ@z> (raw)
Hello,
There is a tool to extract LTT buffers from kernel dump. The general
propose of it is to have flight recorder on linux box.
So that you can run LTT in overwrite mode to keep track about all
system or program events in cycling buffer. When you will get kernel
panic it will be possible to analyze which events were in the system
before crash.
I tried to write it with minimal requirements to external
applications. The latest gdb has so named python macro. So this is
only one single requirement.
Tar ball with sources is attached.
How to use:
1. Compile kernel with:
- kdump support - refer to Documentation/kdump documentation.
- ltt with CONFIG_LTT_VMCORE option.
- debug info is needed to read information from kernel dump.
2. Run LTT in flight recorder mode with -o channel.all.overwrite=1 option.
lttctl -C -w /root/trace1 trace1 -o channel.all.overwrite=1
ltt-armall
3. Get kernel dump from /proc/vmcore and place it in directory with
ltt.py and .gdbinit.
4. Compile helper function, run make.
5. Get buffers from vmcore and save that to file:
gdb vmlinux vmcore
> lttsavebuffers
Directory with trace name will appear (trace1).
6. Apply lttvmcore.patch patch to ltt viewer lttvmcore.patch
7. Show trace:
lttv -m textDump -t ./trace1
--
Best regards,
Maxim Uvarov
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lttvmcoreV01.tar.gz
Type: application/x-gzip
Size: 12090 bytes
Desc: not available
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100819/c54603b4/attachment-0003.bin>
next reply other threads:[~2010-08-19 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 16:53 Maxim Uvarov [this message]
2010-08-19 16:53 ` Maxim Uvarov
2010-08-19 16:53 ` Maxim Uvarov
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=AANLkTik6a-TCO1+tqp-ap-iGE8hYKp0ntBk-iDRKPjQx@mail.gmail.com \
--to=muvarov@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