From mboxrd@z Thu Jan 1 00:00:00 1970 From: minyard@acm.org (Corey Minyard) Date: Tue, 18 Feb 2014 13:29:23 -0600 Subject: [lttng-dev] Extract lttng trace from kernel coredump In-Reply-To: <353610105.9520.1390071650232.JavaMail.zimbra@efficios.com> References: <52D46B33.4010401@acm.org> <20140114184243.GC8177@thessa> <52D5A08F.4020204@acm.org> <1303248645.9400.1390063653581.JavaMail.zimbra@efficios.com> <52DAC820.7000005@acm.org> <353610105.9520.1390071650232.JavaMail.zimbra@efficios.com> Message-ID: <5303B493.7080200@acm.org> 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: