On Friday 27 May 2011, WAROQUIERS Philippe wrote:
> callgrind => ct (this comes from the old "calltree" callgrind name)
Yes.
However, I really dislike the old name "calltree", as the information collected
by callgrind never was a tree (and never will be), but is a call graph. That was
the reason to rename it years ago.
> Following the same logic, if we would have monitor commands for
> cachegrind,
> they would start with cg. (there are no cachegrind monitor command at
> this stage).
Sure. "cg" should be reserved for cachegrind. Everything else would increase
confusion.
> Changing in gdbserver the two letters for callgrind is very easy at this stage
> (as nobody is yet depending on these letters, it is only in Valgrind svn
> 3.7.0).
>
> But if we better change these, what should these 2 letters be ?
Is there a need for vgdb to stick with 2 letters? I much would prefer "clg"
instead. Since years I use the alias clg='valgrind --tool=callgrind', and in
the callgrind sources I use the CLG_ prefix quite often.
For the original matter of this thread, I can imagine a rename from
callgrind_{annotate,control} to clg_{annotate,control}, but not sure that
would have helped the original poster.
Anyway, for a 2-letter option, "cl" seems a lot better than "ct" for me.
Josef
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users