From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Yordan Karadzhov <y.karadz@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: kernel-shark fails to display
Date: Thu, 29 Feb 2024 19:55:11 +0000 [thread overview]
Message-ID: <CADVatmPECgAXGF164YmbqExBA1PCKYJ8ia-UhxWYs+yUpKo7Mg@mail.gmail.com> (raw)
In-Reply-To: <04601fe7-f487-c50c-1b8f-38662e92813f@gmail.com>
Hi Yordan,
On Wed, 28 Feb 2024 at 20:40, Yordan Karadzhov <y.karadz@gmail.com> wrote:
>
> Hi Sudip,
>
> First of all, I am sorry for the very log time it took me to react to
> the problem you found.
No problem. I was also busy and did not get the time to debug the issue further.
>
> I tried reproducing it on few different machines, but I am not able to
> see it. It would be great if you can help me a bit more, so that I can
> figure out what went wrong in your case.
I am wondering if I have messed up something while updating the package.
>
> It seems that the recording itself was successful, but later KernelShark
> fails to open the recorded file. Note that the file (trace.dat) must
> remain in the directory where you started KernelShark even after the
> abortion. Please try to open again this file in KS and check if this
> gives you the same error. If this is the case, send me the trace.dat
> file, so that I can investigate further.
The trace.dat is working, I have been able to open the same trace.dat
file with the previous version of kernelshark.
Next, I tried to open an old trace.dat (created with old kernelshark)
with the latest version and that also failed.
I can send you the trace.dat and also a .deb package for Debian which
you can install and test, but it will take a few days. I can only do
it after the t64 transition is over.
--
Regards
Sudip
next prev parent reply other threads:[~2024-02-29 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 20:50 kernel-shark fails to display Sudip Mukherjee
2024-01-21 17:00 ` Yordan Karadzhov
2024-02-28 20:40 ` Yordan Karadzhov
2024-02-29 19:55 ` Sudip Mukherjee [this message]
2024-03-01 17:48 ` Yordan Karadzhov
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=CADVatmPECgAXGF164YmbqExBA1PCKYJ8ia-UhxWYs+yUpKo7Mg@mail.gmail.com \
--to=sudipm.mukherjee@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=y.karadz@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;
as well as URLs for NNTP newsgroup(s).