linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: Dario Faggioli <dfaggioli@suse.com>,
	Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: Kernelshark v2 all-black plots area
Date: Tue, 9 Feb 2021 15:06:14 +0200	[thread overview]
Message-ID: <ce06b82f-6335-4653-0d27-e48a37ffb5aa@gmail.com> (raw)
In-Reply-To: <89dbef38a1050c31390ce263d51fff1f72a42164.camel@suse.com>

Ciao Dario,

There is a bug in one of the patches from the last patch-set I sent. 
This bug was reported by Tzvetomir. My guess is that you are hitting the 
same issue. If this is the case you must also have an error message 
saying "Unable to find FreeSans font".

You can manually do the fix suggested by Tzvetomir (see his reply to 
[PATCH 15/24] kernel-shark: Update KsDualMarker and KsGLWidget) or just 
get a corrected (rebased) version of the code from
https://github.com/yordan-karadzhov/kernel-shark-v2.beta

Please let me know if this fixes your issue.
Thank you very much for testing and reporting!

Best
Yordan

On 9.02.21 г. 12:48 ч., Dario Faggioli wrote:
> Heya, me again! :-)
> 
> So, I'm not playing with trace-cmd only, I'm also giving a try to
> kernelshark-v2.
> 
> I can build it fine, and it even starts, but the plots area looks
> almost all black. The events and the tasks occurring on the "last CPU"
> (i.e., on CPU7 if I have 8 CPUs) are more or less fine, it seems
> (although still hard to work with, given the background).
> 
> Actually, it's the last plot that "works". In fact, if I add a task
> plot, I do see what that one is supposed to show, but the events of
> CPU7 disappear.
> 
> Others are there, because the marker moves if I click on the entries in
> the trace area... but they're kind of behind the black cover.
> 
> A screenshot can be found here:
> http://xenbits.xen.org/people/dariof/kernelshark-v2-black.png
> 
> Am I the only one? Can it be related to my configuration or build
> environment?
> 
> I'm happy to help with more info or try some debugging, if you think it
> could be useful.
> 
> Thanks and Regards
> 

  reply	other threads:[~2021-02-09 13:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 10:48 Kernelshark v2 all-black plots area Dario Faggioli
2021-02-09 13:06 ` Yordan Karadzhov (VMware) [this message]
2021-02-09 16:13   ` Dario Faggioli
2021-02-10 11:21     ` Yordan Karadzhov (VMware)
2021-02-10 14:51       ` Dario Faggioli
2021-02-10 15:47         ` Yordan Karadzhov (VMware)
2021-02-10 16:15           ` Dario Faggioli
2021-02-10 16:23           ` Steven Rostedt
2022-04-20  0:38   ` Solomon Tan
2022-04-20  8:06     ` Yordan Karadzhov
2022-04-20 15:17       ` Solomon Tan
2022-04-20 15:38         ` [PATCH 1/2] kernel-shark: Make FreeSans a compulsory component Solomon Tan
2022-04-20 15:38           ` [PATCH 2/2] kernel-shark: Allow FreeSans otf in addition to ttf Solomon Tan
2022-04-21 12:16             ` Yordan Karadzhov
2022-04-21 12:04           ` [PATCH 1/2] kernel-shark: Make FreeSans a compulsory component 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=ce06b82f-6335-4653-0d27-e48a37ffb5aa@gmail.com \
    --to=y.karadz@gmail.com \
    --cc=dfaggioli@suse.com \
    --cc=linux-trace-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).