Hi Yuri,

first: what version of KCachegrind is this?
In general, if something looks like a bug, I am very grateful if a bug report
is created for it.

On Thursday 07 October 2010, Yuri wrote:
> I have a profile. I made a copy of it and was changing and viewing the copy.

You did start kcachegrind multiple times, once for the original and once
for the copy. Is this correct?

I.e. you should not use "File/Add profile", as this will give you the 
aggregation
of original and copy.

> Now I notice that when I open the original I see function names that 
> aren't even in the profile, but only in the copy that was opened 
> earlier. And the tree view isn't focusing on functions.

Where do you see these function names?
What do you mean by "the tree view isn't focusing on functions"? But you
still can select them?

When quitting, KCachegrind saves the current browsing state into its config
file, depending on the command whose profile was loaded (this always is
just *one* function, not multiple; therefor my question above).
The idea is that when you start kcachegrind again with this profile (or
another profile generated by the same command), kcachegrind automatically
selects the function and event type etc. where you left the last time.
However, if the function saved in the config is not found, it just should
select "main", or if that is not found, the function with the highest cost.

> I see that kcachegrind saves state in ~/.gconfd/saved-state through gconfd.

Interesting. I do not know since when KDE applications can use the GNOME
infrastructure to store settings (I am not joking, I know that multiple
configuration storage backends are supported, but using the GNOME settings
daemon is new to me).

If the native KDE configuration backend on Linux is used, you can delete
~/.kde4/share/config/kcachegrindrc
 
> But gconf-editor fails to find kcachegrind as an app.

Sorry, no idea.

Josef

> 
> How do I erase the state of my profile?
> 
> Thank you,
> Yuri
> 
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Valgrind-users mailing list
> Valgrind-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
> 



------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to