kcachegrind-callgrind — Discussion around callgrind usage and development

Re: [Kcachegrind-callgrind] meaning of "lr" in Source Code View

[Josef W. <Jos...@gm...>]

Am 28.08.2015 um 12:11 schrieb Simon Brandner:
> When I open a callgrind trace and go the the "Source Code" view, it
> shows a column labelled "lr".
> I have not found any documentation about this value. The numbers seem
> to be very similar to the cycle estimate "CEst" which can be manually
> selected in the View options.

This is "Ir", not "lr".
Usually, KCachegrind should know about this, and use "Instruction Fetch"
as description instead. It is the number of x86 instructions executed.

If you do not use the cache simulator in Callgrind, this actually is the
same as "CEst" = Cycle Estimation = Approximation of time used. This
approximation assumes that time used is proportional to the number of
instructions executed, as there is no other information available without
cache simulation switched on.

Cheers,
Josef

> 
> Can you explain the difference between these two values?
> 
> I am using the 0.7.2kde version on Centos 7.
> 
> Thank you!
> 
> Regards,
> 
> Simon
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Kcachegrind-callgrind mailing list
> Kca...@li...
> https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind
> 

[Kcachegrind-callgrind] meaning of "lr" in Source Code View

[Simon B. <sim...@gm...>]

Hi,

When I open a callgrind trace and go the the "Source Code" view, it
shows a column labelled "lr".
I have not found any documentation about this value. The numbers seem
to be very similar to the cycle estimate "CEst" which can be manually
selected in the View options.

Can you explain the difference between these two values?

I am using the 0.7.2kde version on Centos 7.

Thank you!

Regards,

Simon

Re: [Kcachegrind-callgrind] customizing kcachegrind for limited GNU make profile data

[Rocky B. <ro...@gn...>]

On Mon, Jun 8, 2015 at 2:05 PM, Josef Weidendorfer <
Jos...@gm...> wrote:

> Am 08.06.2015 um 17:32 schrieb Rocky Bernstein:
> > hide the buttons. My take is hide the buttons.
>
> Sounds reasonable.
>

Specifically I'm thinking of hiding the "function cycle" grouping when
there aren't any.  If there are no ELF objects, (I guess no "ob=" in the
callgrind.out file), then a dummy is created to put everything under. But
another possibility is just leaving off that choice of grouping by ELF
objects. Same thing goes with "Class". For a non-OO C program it looks like
a "global" class is created. And for GNU Makefiles, "Class" doesn't make
sense. So perhaps would be just to simplify the grouping and leave that off
as well.


> > And my take is that doing this automatically is preferable
> > to having a user deselect things that aren't applicable.
>
> Sure, some automatism without user involvment is good.
>
> > So is it feasible to remove grouping by ELF object or class in the
> > dropdown and the "Machine Code" tab if there isn't any machine code as
> > determined by the specific data?
>
> Currently KCachegrind has the "machine code" tab visible even
> if there is no data to show, as I want to "teach" users by
> showing a hint for how to enable measurement at machine code level
> (knowing that people do not read manuals).
>

Fair enough. Here is another possibility.  Note that when only one
callgrind.out file is around "Parts" is greyed out. Would it be okay to
also grey out "Machine Code" when there is none but  have the message under
assembly instruction be given as a tool tip when it is greyed out? And
there could be tooltips under the other buttons like "Parts" as well.


> Wouldn't it be enough to extend the profile format with a header
> field to suppress UI elements/features?
>

That would work too, although it would lead to extending the protocol. Let
me know what you would prefer.


>
> Josef
>
> > On Mon, Jun 8, 2015 at 10:15 AM, Josef Weidendorfer
> > <Jos...@gm... <mailto:Jos...@gm...>> wrote:
> >
> >     Hi Rocky,
> >
> >     of course it would be nice to make kcachegrind (or the pure Qt
> version
> >     qcachegrind)
> >     usable for other visualization needs, as long as this makes some
> sense.
> >
> >     What do you actually see missing?
> >     The current format already makes instruction addresses optional, but
> a
> >     more explicit
> >     way to toggle visualizations on/off may be useful.
> >
> >     If you have a patch available, just send it.
> >
> >     Best,
> >     Josef
> >
> >     Am 31.05.2015 um 16:19 schrieb Rocky Bernstein:
> >     > I've recently discovered kcachegrind and it is awesome. I am using
> it to
> >     > show profiling and callgraph data for GNU make runs in afork of
> GNU make
> >     > that adds profiling <http://bashdb.sourceforge.net/remake/>
> >     >
> >     > Of course, in the context of GNU Make profile data, there is an
> analogy
> >     > going on (e.g. stack of target dependencies being made is
> approximately
> >     > a call stack). Not all of the features you would find in profiling
> a
> >     > machine executable are relevant. Specifically, there are no machine
> >     > instructions so the "Machine Code" tab is useless. And "grouping"
> by ELF
> >     > object or Class is also not meaningful.
> >     >
> >     > Is there a way to tell kcachegrind to hide or disable such options?
> >     >
> >     > Thanks.
> >     >
> >     >
> >     >
> ------------------------------------------------------------------------------
> >     >
> >     >
> >     >
> >     > _______________________________________________
> >     > Kcachegrind-callgrind mailing list
> >     > Kca...@li...
> >     <mailto:Kca...@li...>
> >     > https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind
> >     >
> >
> >
>  ------------------------------------------------------------------------------
> >     _______________________________________________
> >     Kcachegrind-callgrind mailing list
> >     Kca...@li...
> >     <mailto:Kca...@li...>
> >     https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> >
> >
> >
> > _______________________________________________
> > Kcachegrind-callgrind mailing list
> > Kca...@li...
> > https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind
> >
>

Re: [Kcachegrind-callgrind] customizing kcachegrind for limited GNU make profile data

[Josef W. <Jos...@gm...>]

Am 08.06.2015 um 17:32 schrieb Rocky Bernstein:
> hide the buttons. My take is hide the buttons.

Sounds reasonable.

> And my take is that doing this automatically is preferable
> to having a user deselect things that aren't applicable.

Sure, some automatism without user involvment is good.

> So is it feasible to remove grouping by ELF object or class in the
> dropdown and the "Machine Code" tab if there isn't any machine code as
> determined by the specific data? 

Currently KCachegrind has the "machine code" tab visible even
if there is no data to show, as I want to "teach" users by
showing a hint for how to enable measurement at machine code level
(knowing that people do not read manuals).

Wouldn't it be enough to extend the profile format with a header
field to suppress UI elements/features?

Josef

> On Mon, Jun 8, 2015 at 10:15 AM, Josef Weidendorfer
> <Jos...@gm... <mailto:Jos...@gm...>> wrote:
> 
>     Hi Rocky,
> 
>     of course it would be nice to make kcachegrind (or the pure Qt version
>     qcachegrind)
>     usable for other visualization needs, as long as this makes some sense.
> 
>     What do you actually see missing?
>     The current format already makes instruction addresses optional, but a
>     more explicit
>     way to toggle visualizations on/off may be useful.
> 
>     If you have a patch available, just send it.
> 
>     Best,
>     Josef
> 
>     Am 31.05.2015 um 16:19 schrieb Rocky Bernstein:
>     > I've recently discovered kcachegrind and it is awesome. I am using it to
>     > show profiling and callgraph data for GNU make runs in afork of GNU make
>     > that adds profiling <http://bashdb.sourceforge.net/remake/>
>     >
>     > Of course, in the context of GNU Make profile data, there is an analogy
>     > going on (e.g. stack of target dependencies being made is approximately
>     > a call stack). Not all of the features you would find in profiling a
>     > machine executable are relevant. Specifically, there are no machine
>     > instructions so the "Machine Code" tab is useless. And "grouping" by ELF
>     > object or Class is also not meaningful.
>     >
>     > Is there a way to tell kcachegrind to hide or disable such options?
>     >
>     > Thanks.
>     >
>     >
>     > ------------------------------------------------------------------------------
>     >
>     >
>     >
>     > _______________________________________________
>     > Kcachegrind-callgrind mailing list
>     > Kca...@li...
>     <mailto:Kca...@li...>
>     > https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind
>     >
> 
>     ------------------------------------------------------------------------------
>     _______________________________________________
>     Kcachegrind-callgrind mailing list
>     Kca...@li...
>     <mailto:Kca...@li...>
>     https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> 
> 
> 
> _______________________________________________
> Kcachegrind-callgrind mailing list
> Kca...@li...
> https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind
> 

Re: [Kcachegrind-callgrind] customizing kcachegrind for limited GNU make profile data

[Rocky B. <ro...@gn...>]

If we agree on an acceptable way to accomplish the simplification, perhaps
I'll work something up.

The big picture is that while kcachegrind has a lot of features and many of
them are cool, there are number of situations where buttons aren't
applicable. In those cases, I think it would be great to grey out or hide
the buttons. My take is hide the buttons. And my take is that doing this
automatically is preferable to having a user deselect things that aren't
applicable.

So is it feasible to remove grouping by ELF object or class in the dropdown
and the "Machine Code" tab if there isn't any machine code as determined by
the specific data?

On Mon, Jun 8, 2015 at 10:15 AM, Josef Weidendorfer <
Jos...@gm...> wrote:

> Hi Rocky,
>
> of course it would be nice to make kcachegrind (or the pure Qt version
> qcachegrind)
> usable for other visualization needs, as long as this makes some sense.
>
> What do you actually see missing?
> The current format already makes instruction addresses optional, but a
> more explicit
> way to toggle visualizations on/off may be useful.
>
> If you have a patch available, just send it.
>
> Best,
> Josef
>
> Am 31.05.2015 um 16:19 schrieb Rocky Bernstein:
> > I've recently discovered kcachegrind and it is awesome. I am using it to
> > show profiling and callgraph data for GNU make runs in afork of GNU make
> > that adds profiling <http://bashdb.sourceforge.net/remake/>
> >
> > Of course, in the context of GNU Make profile data, there is an analogy
> > going on (e.g. stack of target dependencies being made is approximately
> > a call stack). Not all of the features you would find in profiling a
> > machine executable are relevant. Specifically, there are no machine
> > instructions so the "Machine Code" tab is useless. And "grouping" by ELF
> > object or Class is also not meaningful.
> >
> > Is there a way to tell kcachegrind to hide or disable such options?
> >
> > Thanks.
> >
> >
> >
> ------------------------------------------------------------------------------
> >
> >
> >
> > _______________________________________________
> > Kcachegrind-callgrind mailing list
> > Kca...@li...
> > https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind
> >
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Kcachegrind-callgrind mailing list
> Kca...@li...
> https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind
>

Re: [Kcachegrind-callgrind] customizing kcachegrind for limited GNU make profile data

[Josef W. <Jos...@gm...>]

Hi Rocky,

of course it would be nice to make kcachegrind (or the pure Qt version
qcachegrind)
usable for other visualization needs, as long as this makes some sense.

What do you actually see missing?
The current format already makes instruction addresses optional, but a
more explicit
way to toggle visualizations on/off may be useful.

If you have a patch available, just send it.

Best,
Josef

Am 31.05.2015 um 16:19 schrieb Rocky Bernstein:
> I've recently discovered kcachegrind and it is awesome. I am using it to
> show profiling and callgraph data for GNU make runs in afork of GNU make
> that adds profiling <http://bashdb.sourceforge.net/remake/>
> 
> Of course, in the context of GNU Make profile data, there is an analogy
> going on (e.g. stack of target dependencies being made is approximately
> a call stack). Not all of the features you would find in profiling a
> machine executable are relevant. Specifically, there are no machine
> instructions so the "Machine Code" tab is useless. And "grouping" by ELF
> object or Class is also not meaningful.
> 
> Is there a way to tell kcachegrind to hide or disable such options? 
> 
> Thanks.
> 
> 
> ------------------------------------------------------------------------------
> 
> 
> 
> _______________________________________________
> Kcachegrind-callgrind mailing list
> Kca...@li...
> https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind
> 

[Kcachegrind-callgrind] customizing kcachegrind for limited GNU make profile data

[Rocky B. <ro...@gn...>]

I've recently discovered kcachegrind and it is awesome. I am using it to
show profiling and callgraph data for GNU make runs in a fork of GNU make
that adds profiling <http://bashdb.sourceforge.net/remake/>

Of course, in the context of GNU Make profile data, there is an analogy
going on (e.g. stack of target dependencies being made is approximately a
call stack). Not all of the features you would find in profiling a machine
executable are relevant. Specifically, there are no machine instructions so
the "Machine Code" tab is useless. And "grouping" by ELF object or Class is
also not meaningful.

Is there a way to tell kcachegrind to hide or disable such options?

Thanks.

Re: [Kcachegrind-callgrind] KCachegrind freezes (UNCLASSIFIED)

[Glasgow, S. R C. U. T. A. C. (US) <ste...@ma...>]

Classification: UNCLASSIFIED
Caveats: NONE

WHOOO HOOO!!!!

Upgraded to version 0.7.2 and everything is working!

THANKS!!
Steve

-----Original Message-----
From: Josef Weidendorfer [mailto:Jos...@gm...] 
Sent: Wednesday, March 27, 2013 12:14 PM
To: kca...@li...
Subject: Re: [Kcachegrind-callgrind] KCachegrind freezes (UNCLASSIFIED)

Am 27.03.2013 15:08, schrieb Glasgow, Steven
> KDE 4.3.4
>
> valgrind 3.8.1
>
> KCachegrind 0.5.1kde
>
> After running the following:
>
> valgrind-tool=callgrind<application> <argument>
>
> I try to load thecallgrind.out.<pid> file into KCachegrind and the GUI 
> freezes immediately.  It displays informationon the left (Flat 
> Profile) then locks up. NOTHING works, not even the menu items.  
> Clicking the close button provided by KDE (top right) informs me that 
> KCachegrind is not responding and asks me to force quit.

0.5.1 is quite old. Can you try a newer version?
You can check out the current version (0.7.2) with

  git clone git://anongit.kde.org/kcachegrind.git

It should compile on KDE 4.3.4 (check the README).

> What could be causing this?

Perhaps some infinite loop in the cycle detection algorithm, which is run
after loading the data, but this is pure speculation.

If this problem persists in the newest version, I need to be able to
reproduce it (you could send me the profile file, if that is possible).

Josef

>
> Thanks,
>
> Steve
>
> Classification: UNCLASSIFIED
>
> Caveats: NONE
>
>
>
> ----------------------------------------------------------------------
> -------- Own the Future-Intel&reg; Level Up Game Demo Contest 2013 
> Rise to greatness in Intel's independent game demo contest.
> Compete for recognition, cash, and the chance to get your game on 
> Steam. $5K grand prize plus 10 genre and skill prizes.
> Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
>
>
>
> _______________________________________________
> Kcachegrind-callgrind mailing list
> Kca...@li...
> https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind
>


----------------------------------------------------------------------------
--
Own the Future-Intel&reg; Level Up Game Demo Contest 2013 Rise to greatness
in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game on Steam. $5K
grand prize plus 10 genre and skill prizes. 
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
_______________________________________________
Kcachegrind-callgrind mailing list
Kca...@li...
https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind

Classification: UNCLASSIFIED
Caveats: NONE

Re: [Kcachegrind-callgrind] KCachegrind freezes (UNCLASSIFIED)

[Glasgow, S. R C. U. T. A. C. (US) <ste...@ma...>]

Classification: UNCLASSIFIED
Caveats: NONE

I thought 0.7.3 was the latest according to
http://kcachegrind.sourceforge.net/html/Download.html

Thanks,
Steve

-----Original Message-----
From: Glasgow, Steven R CIV USARMY TRADOC ANALYSIS CTR (US)
[mailto:ste...@ma...] 
Sent: Wednesday, March 27, 2013 2:53 PM
To: kca...@li...
Subject: Re: [Kcachegrind-callgrind] KCachegrind freezes (UNCLASSIFIED)

Classification: UNCLASSIFIED
Caveats: NONE

Thank you,

I'll get our support staff to upgrade it.

Thanks,
Steve

-----Original Message-----
From: Josef Weidendorfer [mailto:Jos...@gm...]
Sent: Wednesday, March 27, 2013 12:14 PM
To: kca...@li...
Subject: Re: [Kcachegrind-callgrind] KCachegrind freezes (UNCLASSIFIED)

Am 27.03.2013 15:08, schrieb Glasgow, Steven
> KDE 4.3.4
>
> valgrind 3.8.1
>
> KCachegrind 0.5.1kde
>
> After running the following:
>
> valgrind-tool=callgrind<application> <argument>
>
> I try to load thecallgrind.out.<pid> file into KCachegrind and the GUI 
> freezes immediately.  It displays informationon the left (Flat
> Profile) then locks up. NOTHING works, not even the menu items.  
> Clicking the close button provided by KDE (top right) informs me that 
> KCachegrind is not responding and asks me to force quit.

0.5.1 is quite old. Can you try a newer version?
You can check out the current version (0.7.2) with

  git clone git://anongit.kde.org/kcachegrind.git

It should compile on KDE 4.3.4 (check the README).

> What could be causing this?

Perhaps some infinite loop in the cycle detection algorithm, which is run
after loading the data, but this is pure speculation.

If this problem persists in the newest version, I need to be able to
reproduce it (you could send me the profile file, if that is possible).

Josef

>
> Thanks,
>
> Steve
>
> Classification: UNCLASSIFIED
>
> Caveats: NONE
>
>
>
> ----------------------------------------------------------------------
> -------- Own the Future-Intel&reg; Level Up Game Demo Contest 2013 
> Rise to greatness in Intel's independent game demo contest.
> Compete for recognition, cash, and the chance to get your game on 
> Steam. $5K grand prize plus 10 genre and skill prizes.
> Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
>
>
>
> _______________________________________________
> Kcachegrind-callgrind mailing list
> Kca...@li...
> https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind
>


----------------------------------------------------------------------------
--
Own the Future-Intel&reg; Level Up Game Demo Contest 2013 Rise to greatness
in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game on Steam. $5K
grand prize plus 10 genre and skill prizes. 
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
_______________________________________________
Kcachegrind-callgrind mailing list
Kca...@li...
https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind

Classification: UNCLASSIFIED
Caveats: NONE



Classification: UNCLASSIFIED
Caveats: NONE

Re: [Kcachegrind-callgrind] KCachegrind freezes (UNCLASSIFIED)

[Glasgow, S. R C. U. T. A. C. (US) <ste...@ma...>]

Classification: UNCLASSIFIED
Caveats: NONE

Thank you,

I'll get our support staff to upgrade it.

Thanks,
Steve

-----Original Message-----
From: Josef Weidendorfer [mailto:Jos...@gm...] 
Sent: Wednesday, March 27, 2013 12:14 PM
To: kca...@li...
Subject: Re: [Kcachegrind-callgrind] KCachegrind freezes (UNCLASSIFIED)

Am 27.03.2013 15:08, schrieb Glasgow, Steven
> KDE 4.3.4
>
> valgrind 3.8.1
>
> KCachegrind 0.5.1kde
>
> After running the following:
>
> valgrind-tool=callgrind<application> <argument>
>
> I try to load thecallgrind.out.<pid> file into KCachegrind and the GUI 
> freezes immediately.  It displays informationon the left (Flat 
> Profile) then locks up. NOTHING works, not even the menu items.  
> Clicking the close button provided by KDE (top right) informs me that 
> KCachegrind is not responding and asks me to force quit.

0.5.1 is quite old. Can you try a newer version?
You can check out the current version (0.7.2) with

  git clone git://anongit.kde.org/kcachegrind.git

It should compile on KDE 4.3.4 (check the README).

> What could be causing this?

Perhaps some infinite loop in the cycle detection algorithm, which is run
after loading the data, but this is pure speculation.

If this problem persists in the newest version, I need to be able to
reproduce it (you could send me the profile file, if that is possible).

Josef

>
> Thanks,
>
> Steve
>
> Classification: UNCLASSIFIED
>
> Caveats: NONE
>
>
>
> ----------------------------------------------------------------------
> -------- Own the Future-Intel&reg; Level Up Game Demo Contest 2013 
> Rise to greatness in Intel's independent game demo contest.
> Compete for recognition, cash, and the chance to get your game on 
> Steam. $5K grand prize plus 10 genre and skill prizes.
> Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
>
>
>
> _______________________________________________
> Kcachegrind-callgrind mailing list
> Kca...@li...
> https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind
>


----------------------------------------------------------------------------
--
Own the Future-Intel&reg; Level Up Game Demo Contest 2013 Rise to greatness
in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game on Steam. $5K
grand prize plus 10 genre and skill prizes. 
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
_______________________________________________
Kcachegrind-callgrind mailing list
Kca...@li...
https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind

Classification: UNCLASSIFIED
Caveats: NONE

Re: [Kcachegrind-callgrind] KCachegrind freezes (UNCLASSIFIED)

[Josef W. <Jos...@gm...>]

Am 27.03.2013 15:08, schrieb Glasgow, Steven
> KDE 4.3.4
>
> valgrind 3.8.1
>
> KCachegrind 0.5.1kde
>
> After running the following:
>
> valgrind–tool=callgrind<application> <argument>
>
> I try to load thecallgrind.out.<pid> file into KCachegrind and the GUI
> freezes immediately.  It displays informationon the left (Flat Profile)
> then locks up. NOTHING works, not even the menu items.  Clicking the
> close button provided by KDE (top right) informs me that KCachegrind is
> not responding and asks me to force quit.

0.5.1 is quite old. Can you try a newer version?
You can check out the current version (0.7.2) with

  git clone git://anongit.kde.org/kcachegrind.git

It should compile on KDE 4.3.4 (check the README).

> What could be causing this?

Perhaps some infinite loop in the cycle detection algorithm,
which is run after loading the data, but this is pure speculation.

If this problem persists in the newest version, I need to be able
to reproduce it (you could send me the profile file, if that is
possible).

Josef

>
> Thanks,
>
> Steve
>
> Classification: UNCLASSIFIED
>
> Caveats: NONE
>
>
>
> ------------------------------------------------------------------------------
> Own the Future-Intel&reg; Level Up Game Demo Contest 2013
> Rise to greatness in Intel's independent game demo contest.
> Compete for recognition, cash, and the chance to get your game
> on Steam. $5K grand prize plus 10 genre and skill prizes.
> Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
>
>
>
> _______________________________________________
> Kcachegrind-callgrind mailing list
> Kca...@li...
> https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind
>

[Kcachegrind-callgrind] KCachegrind freezes (UNCLASSIFIED)

[Glasgow, S. R C. U. T. A. C. (US) <ste...@ma...>]

Classification: UNCLASSIFIED
Caveats: NONE

My environment:

RHEL 6.3
KDE 4.3.4
valgrind 3.8.1
KCachegrind 0.5.1kde

After running the following:

valgrind -tool=callgrind <application> <argument>

I try to load the callgrind.out.<pid> file into KCachegrind and the GUI
freezes immediately.  It displays information on the left (Flat Profile)
then locks up.  NOTHING works, not even the menu items.  Clicking the close
button provided by KDE (top right) informs me that KCachegrind is not
responding and asks me to force quit.

What could be causing this?

Thanks,
Steve

Classification: UNCLASSIFIED
Caveats: NONE

Re: [Kcachegrind-callgrind] Support for mips64 objdump format.

[David N. <Dav...@en...>]

Oops, just noticed a typo in the cpp comments. Fixing ... 

diff -Naur kcachegrind-0.4.6/kcachegrind/instrview.cpp kcachegrind-0.4.6.new/kcachegrind/instrview.cpp
--- kcachegrind-0.4.6/kcachegrind/instrview.cpp 2005-09-27 00:43:04.000000000 +0200
+++ kcachegrind-0.4.6.new/kcachegrind/instrview.cpp     2011-10-31 07:10:41.700697425 +0100
@@ -80,5 +80,24 @@
         if (buf[pos2+2] != ' ') break;
         pos2 += 3;
     }
-    buf[pos2-1]=0;
+    if (pos2 <= pos1) {
+      // skip code, pattern "xxxxxxxx "*
+      // Try again with the "ffffff "* format 
+
+      for (pos1 = pos2;; pos2++) {
+       // Won't handle more than a 64-bit hex instruction
+       if (pos2 - pos1 >= 16) {
+         if (0) qDebug("Instruction > 64 bit, wont interpret on line: %u", __LINE__);
+         return false;
+       }
+      
+       if (! ((buf[pos2]>='0' && buf[pos2]<='9') ||
+              (buf[pos2]>='a' && buf[pos2]<='f')) ) break;     
+      }
+      pos2++;
+    }
+   
+    buf[pos2-1]=0;
+  
+
     while(buf[pos2]==' '|| buf[pos2]=='\t') pos2++;
________________________________________
From: David Nyström [Dav...@en...]
Sent: Monday, October 31, 2011 07:20
To: kca...@li...
Subject: [Kcachegrind-callgrind] Support for mips64 objdump format.

Added support for no spaced hex instructional view in objdump format, "ffffff "* format.

Best Regards,
David Nyström

diff -Naur kcachegrind-0.4.6/kcachegrind/instrview.cpp kcachegrind-0.4.6.new/kcachegrind/instrview.cpp
--- kcachegrind-0.4.6/kcachegrind/instrview.cpp 2005-09-27 00:43:04.000000000 +0200
+++ kcachegrind-0.4.6.new/kcachegrind/instrview.cpp     2011-10-31 07:10:41.700697425 +0100
@@ -80,5 +80,24 @@
        if (buf[pos2+2] != ' ') break;
        pos2 += 3;
     }
-    buf[pos2-1]=0;
+    if (pos2 <= pos1) {
+      // skip code, pattern "xxxxxxxx "*
+      // Try again with the "ffffff "* format */
+
+      for (pos1 = pos2;; pos2++) {
+       // Won't handle more than a 64-bit hex instruction
+       if (pos2 - pos1 >= 16) {
+         if (0) qDebug("Instruction > 64 bit, wont interpret on line: %u", __LINE__);
+         return false;
+       }
+
+       if (! ((buf[pos2]>='0' && buf[pos2]<='9') ||
+              (buf[pos2]>='a' && buf[pos2]<='f')) ) break;
+      }
+      pos2++;
+    }
+
+    buf[pos2-1]=0;
+
+
     while(buf[pos2]==' '|| buf[pos2]=='\t') pos2++;





------------------------------------------------------------------------------
Get your Android app more play: Bring it to the BlackBerry PlayBook
in minutes. BlackBerry App World&#153; now supports Android&#153; Apps
for the BlackBerry&reg; PlayBook&#153;. Discover just how easy and simple
it is! http://p.sf.net/sfu/android-dev2dev
_______________________________________________
Kcachegrind-callgrind mailing list
Kca...@li...
https://lists.sourceforge.net/lists/listinfo/kcachegrind-callgrind

[Kcachegrind-callgrind] Support for mips64 objdump format.

[David N. <Dav...@en...>]

Added support for no spaced hex instructional view in objdump format, "ffffff "* format.

Best Regards,
David Nyström

diff -Naur kcachegrind-0.4.6/kcachegrind/instrview.cpp kcachegrind-0.4.6.new/kcachegrind/instrview.cpp
--- kcachegrind-0.4.6/kcachegrind/instrview.cpp	2005-09-27 00:43:04.000000000 +0200
+++ kcachegrind-0.4.6.new/kcachegrind/instrview.cpp	2011-10-31 07:10:41.700697425 +0100
@@ -80,5 +80,24 @@
 	if (buf[pos2+2] != ' ') break;
 	pos2 += 3;
     }
-    buf[pos2-1]=0;
+    if (pos2 <= pos1) {
+      // skip code, pattern "xxxxxxxx "*
+      // Try again with the "ffffff "* format */
+
+      for (pos1 = pos2;; pos2++) {
+	// Won't handle more than a 64-bit hex instruction
+	if (pos2 - pos1 >= 16) {
+	  if (0) qDebug("Instruction > 64 bit, wont interpret on line: %u", __LINE__);
+	  return false;
+	}
+	
+	if (! ((buf[pos2]>='0' && buf[pos2]<='9') ||
+	       (buf[pos2]>='a' && buf[pos2]<='f')) ) break;	
+      }
+      pos2++;
+    }
+    
+    buf[pos2-1]=0;
+   
+
     while(buf[pos2]==' '|| buf[pos2]=='\t') pos2++;

Re: [Kcachegrind-callgrind] Building kcachegrind 0.7.0 on RHEL 6

[Josef W. <Jos...@gm...>]

Hi Ladar,

thanks for the instructions. I do not install qcachegrind on purpose when compiling
with CMake, as I do not see the point to have both kcachegrind and qcachegrind installed.
Anyway, the instructions are helpful for people.

Cheers,
Josef

On Friday 02 September 2011, Ladar Levison wrote:
> *You might want to update the readme/website. Using CMake the commands are:*
> 
> cmake -D QT_MOC_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/moc -D 
> QT_UIC_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/uic .
> make
> sudo make install
> sudo install -m 755 qcachegrind/qcachegrind /usr/local/bin
> sudo install -m 644 qcachegrind/qcachegrind.desktop 
> /usr/local/share/applications/
> sudo install -m 644 kcachegrind/hi32-app-kcachegrind.png 
> /usr/local/share/icons/hicolor/32x32/apps/kcachegrind.png
> sudo install -m 644 kcachegrind/hi48-app-kcachegrind.png 
> /usr/local/share/icons/hicolor/48x48/apps/kcachegrind.png
> 
> 
> 
> 
> *And if someone wants to build via Qmake:*
> 
> sed -i -e "s/new_moc.commands = moc/new_moc.commands = 
> \/usr\/lib64\/qt4\/bin\/moc/g/" qcachegrind/qcachegrind.pro
> 
> /usr/lib64/qt4/bin/qmake -spec linux-g++
> make
> sudo install -m 755 qcachegrind /usr/local/bin
> sudo install -m 644 qcachegrind.desktop /usr/local/share/applications/
> sudo install -m 644 hi32-app-kcachegrind.png 
> /usr/local/share/icons/hicolor/32x32/apps/kcachegrind.png
> sudo install -m 644 hi48-app-kcachegrind.png 
> /usr/local/share/icons/hicolor/48x48/apps/kcachegrind.png
> 
> 

[Kcachegrind-callgrind] Building kcachegrind 0.7.0 on RHEL 6

[Ladar L. <la...@la...>]

*You might want to update the readme/website. Using CMake the commands are:*

cmake -D QT_MOC_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/moc -D 
QT_UIC_EXECUTABLE:FILEPATH=/usr/lib64/qt4/bin/uic .
make
sudo make install
sudo install -m 755 qcachegrind/qcachegrind /usr/local/bin
sudo install -m 644 qcachegrind/qcachegrind.desktop 
/usr/local/share/applications/
sudo install -m 644 kcachegrind/hi32-app-kcachegrind.png 
/usr/local/share/icons/hicolor/32x32/apps/kcachegrind.png
sudo install -m 644 kcachegrind/hi48-app-kcachegrind.png 
/usr/local/share/icons/hicolor/48x48/apps/kcachegrind.png




*And if someone wants to build via Qmake:*

sed -i -e "s/new_moc.commands = moc/new_moc.commands = 
\/usr\/lib64\/qt4\/bin\/moc/g/" qcachegrind/qcachegrind.pro

/usr/lib64/qt4/bin/qmake -spec linux-g++
make
sudo install -m 755 qcachegrind /usr/local/bin
sudo install -m 644 qcachegrind.desktop /usr/local/share/applications/
sudo install -m 644 hi32-app-kcachegrind.png 
/usr/local/share/icons/hicolor/32x32/apps/kcachegrind.png
sudo install -m 644 hi48-app-kcachegrind.png 
/usr/local/share/icons/hicolor/48x48/apps/kcachegrind.png

[Kcachegrind-callgrind] KCachegrind instruction view for ARM

[Prasad H. L. <hl...@gm...>]

Hi,

I have a native application written an running on Android device which
is an ARM based development platform. Also, I have valgrind
operational on the same. I'm able to view the generated profile
successfully on kcachegrind (running on a PC) and also I'm able to see
annotated source code. However, I have some issues seeing the
annotated assembly. I've specified the right "objdump" executable in
the path and kcachegrind is not giving me any errors in the "Machine
Code" tab. However, in that tab, I'm seeing several lines of "..."
present and no assembly lines displayed whatsoever. Any ideas?

Regards,
Prasad

Re: [Kcachegrind-callgrind] Problems installing KCachegrind

[Josef W. <Jos...@gm...>]

Hi Nigel,

On Wednesday 03 August 2011, Nigel Robbins wrote:
> My RHEL 5 system runs in a VMWare image with few packages installed and yum fails with:
> # yum install kdesdk
> Loaded plugins: rhnplugin, security
> There was an error communicating with RHN.
> RHN support will be disabled.

I am not really sure what RHN stands for, but I assume that is the place where
your distribution tries to get packages from. So this definitely is a Red Had
problem.

> Error communicating with server. The message was:
> Connection refused
>  
> I then downloaded the qt and kdelibs rpms and tried installing them but there were lots of dependencies.

Resolving dependencies is the job of e.g. "yum". So sure, doing this by hand is
not the best way, but I can not really help here.

> Is there an easier way for me to install KCachegrind ?

Installing the distribution packages for sure is the easiest way I can imagine.

I have a pure-Qt version in development, which is quite stable, but not released
yet. Check the sources out from KDE SVN at
 svn://anonsvn.kde.org/home/kde/trunk/KDE/kdesdk/kcachegrind

Go to qcachegrind subdirectory, run "qmake; make", and you get should get a nice,
self-contained "qcachegrind".

Cheers,
Josef

[Kcachegrind-callgrind] Problems installing KCachegrind

[Nigel R. <nig...@ho...>]

Hi,
 
I’ve been profiling my C/C++ application on RHEL 5 using callgrind via valgrind.
 
The output looks very interesting and I really like the look of KCachegrind for visualising the output.
 
My RHEL 5 system runs in a VMWare image with few packages installed and yum fails with:
# yum install kdesdk
Loaded plugins: rhnplugin, security
There was an error communicating with RHN.
RHN support will be disabled.
Error communicating with server. The message was:
Connection refused
 
I then downloaded the qt and kdelibs rpms and tried installing them but there were lots of dependencies.
 
Is there an easier way for me to install KCachegrind ?
 
Thanks,
Nigel 		 	   		  

Re: [Kcachegrind-callgrind] about kcachegrind instaling error

[Josef W. <Jos...@gm...>]

On Friday 06 May 2011, Kaveri Zanje wrote:
> checking for Qt... configure: error: Qt (>= Qt 3.0) (headers and libraries)
> not found. Please check your installation!

That should be "... error: Qt 3.x not found."
For a newer version, use the one found in the KDE distribution (package kdesdk).

If I find some time, I will do a separate release.

Josef


> 
> I have set QTDIR
> 

[Kcachegrind-callgrind] about kcachegrind instaling error

[Kaveri Z. <kav...@gm...>]

checking for Qt... configure: error: Qt (>= Qt 3.0) (headers and libraries)
not found. Please check your installation!

I have set QTDIR

Re: [Kcachegrind-callgrind] Kcachegrind 0.4.6 : configure: error QT (>= QT3, 0) headers and libraries not found

[Josef W. <Jos...@gm...>]

On Thursday 28 April 2011, Frank Chang wrote:
> 
>    Josef Weidenorfer, Thank you for your instructions. Using root, I ran: yum install kdesdk on Centos Linux 5.5 x86_32. After the installation was completed, I located the kcachegrind binary in /usr/bin/kcachegrind. The date-time stamp of the kcachegrind is Jan 6 2007. 
>    I was wondering whether I am using the most recent version of cachegrind. If there is a more recent version of kcachegrind, may I build it using the kdesdk package I just installed on Centos Linux 5.5 x86_32. Thank you for all of your help.

There were only slight changes in recent years (and the mentioned port to Qt4/KDE4), and no big bug fixes
were needed. So even the old version you have installed should meet your needs

Josef

Re: [Kcachegrind-callgrind] Kcachegrind 0.4.6 : configure: error QT (>= QT3, 0) headers and libraries not found

[Frank C. <fra...@ho...>]

   Josef Weidenorfer, Thank you for your instructions. Using root, I ran: yum install kdesdk on Centos Linux 5.5 x86_32. After the installation was completed, I located the kcachegrind binary in /usr/bin/kcachegrind. The date-time stamp of the kcachegrind is Jan 6 2007. 
   I was wondering whether I am using the most recent version of cachegrind. If there is a more recent version of kcachegrind, may I build it using the kdesdk package I just installed on Centos Linux 5.5 x86_32. Thank you for all of your help.
 
> From: Jos...@gm...
> To: kca...@li...
> Subject: Re: [Kcachegrind-callgrind] Kcachegrind 0.4.6 : configure: error QT (>= QT3, 0) headers and libraries not found
> Date: Thu, 28 Apr 2011 18:00:06 +0200
> CC: fra...@ho...
> 
> On Thursday 28 April 2011, Frank Chang wrote:
> > 
> > Good morning, We are running Centos-Linux 5.5 x86+32. I just downloaded kachegrind 0.4.6. When I configure it, it complains about QT: configure: error QT (>= QT3,0) headers and libraries not found.
> > I downloaded QT SDK for Open source Development on Linux/X11 32-bit in my home directory /home/frankc. 
> > When I configure kcachegrind again, it complains about QT: configure: error QT (>= QT3,0) headers and libraries not found even though I downloaded the QT SDK in /home/frankc.
> > Is there any other location I should be installing QT in (maybe as root) so that the kachegrind configure can find the QT header and libraries? Thank you.
> > 
> 
> The code from kcachegrind.sf.net is quite old, and uses Qt 3.x. However, the current Qt version
> is 4.x (newest one is Qt 4.7, included in the Qt SDK, as far as I know). You can not compile that
> source with Qt4.
> 
> For recent KCachegrind sources compiling with Qt4 (and KDE4), check out the KDE source package
> of Centos. There should be one called kdesdk or similar, providing the kcachegrind binary.
> Alternatively, get the sources of a recent version of the KDE package "kdesdk", go into the
> kcachegrind/ subdirectory, run "cmake; make" which should build the kcachegrind binary.
> 
> Best,
> Josef
> 
 		 	   		  

Re: [Kcachegrind-callgrind] Kcachegrind 0.4.6 : configure: error QT (>= QT3, 0) headers and libraries not found

[Josef W. <Jos...@gm...>]

On Thursday 28 April 2011, Frank Chang wrote:
> 
> Good morning, We are running Centos-Linux 5.5 x86+32. I just downloaded kachegrind 0.4.6. When I configure it, it complains about QT: configure: error QT (>= QT3,0) headers and libraries not found.
>      I downloaded QT SDK for Open source Development on Linux/X11 32-bit in my home directory /home/frankc. 
>     When I configure kcachegrind again, it complains about QT: configure: error QT (>= QT3,0) headers and libraries not found even though I downloaded the QT SDK in /home/frankc.
>     Is there any other location I should be installing QT in (maybe as root) so that the kachegrind configure can find the QT header and libraries? Thank you.
>     

The code from kcachegrind.sf.net is quite old, and uses Qt 3.x. However, the current Qt version
is 4.x (newest one is Qt 4.7, included in the Qt SDK, as far as I know). You can not compile that
source with Qt4.

For recent KCachegrind sources compiling with Qt4 (and KDE4), check out the KDE source package
of Centos. There should be one called kdesdk or similar, providing the kcachegrind binary.
Alternatively, get the sources of a recent version of the KDE package "kdesdk", go into the
kcachegrind/ subdirectory, run "cmake; make" which should build the kcachegrind binary.

Best,
Josef

[Kcachegrind-callgrind] Kcachegrind 0.4.6 : configure: error QT (>= QT3, 0) headers and libraries not found

[Frank C. <fra...@ho...>]

Good morning, We are running Centos-Linux 5.5 x86+32. I just downloaded kachegrind 0.4.6. When I configure it, it complains about QT: configure: error QT (>= QT3,0) headers and libraries not found.
     I downloaded QT SDK for Open source Development on Linux/X11 32-bit in my home directory /home/frankc. 
    When I configure kcachegrind again, it complains about QT: configure: error QT (>= QT3,0) headers and libraries not found even though I downloaded the QT SDK in /home/frankc.
    Is there any other location I should be installing QT in (maybe as root) so that the kachegrind configure can find the QT header and libraries? Thank you.