From: Yordan Karadzhov <y.karadz@gmail.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: kernel-shark fails to display
Date: Wed, 28 Feb 2024 22:40:15 +0200 [thread overview]
Message-ID: <04601fe7-f487-c50c-1b8f-38662e92813f@gmail.com> (raw)
In-Reply-To: <CADVatmNXhhn6xhL-=rYqDaHqp4Ct+_i5N42KpeJnnxwoH1Ee+A@mail.gmail.com>
Hi Sudip,
First of all, I am sorry for the very log time it took me to react to
the problem you found.
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.
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.
Thanks!
Yordan
On 1/20/24 22:50, Sudip Mukherjee wrote:
> Hi,
>
> I am seeing a problem with the latest version v2.3.0
> Steps to reproduce:
> 1. start kernel-shark
> 2. Go to Record in Tools menu
> 3. Select Events: All
> 4. Select "Display output"
> 5. Click on Apply
> 6. Click on Capture
>
> It fails with:
> kernelshark: ./src/libkshark-model.c:249: ksmodel_set_upper_edge:
> Assertion `row != BSEARCH_ALL_GREATER' failed.
> Aborted
>
>
next prev parent reply other threads:[~2024-02-28 20:40 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 [this message]
2024-02-29 19:55 ` Sudip Mukherjee
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=04601fe7-f487-c50c-1b8f-38662e92813f@gmail.com \
--to=y.karadz@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sudipm.mukherjee@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).