Re: [Valgrind-users] Possible Error: C​allgrind Version 3.6.1 cg_annotat​​e : Line 1 Missing command line

2011-05-27 Thread Florian Krohm
On 05/27/2011 01:22 PM, Josef Weidendorfer wrote: > On Friday 27 May 2011, WAROQUIERS Philippe wrote: > >> 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). >> Good. >> But if

Re: [Valgrind-users] Possible Error: C​allgrind Version 3.6.1 cg_annotat​​e : Line 1 Missing command line

2011-05-27 Thread Josef Weidendorfer
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 t

Re: [Valgrind-users] Possible Error: C​allgrind Version 3.6.1 cg_annotat​​e : Line 1 Missing command line

2011-05-27 Thread WAROQUIERS Philippe
>> > > cg_annotate is the tool for cachegrind output. >> > > The naming is a little bit unfortunate. >> > Definitely. How about renaming cg_annotate to cachegrind_annotate? With the introduction of the gdbserver in Valgrind (3.7.0 svn), the 'cg' prefix (for cachegrind) versus 'ct' prefix (for ca

Re: [Valgrind-users] Possible Error: C​allgrind Version 3.6.1 cg_annotat​​e : Line 1 Missing command line

2011-05-27 Thread Julian Seward
On Wednesday, May 25, 2011, Josef Weidendorfer wrote: > On Wednesday 25 May 2011, Florian Krohm wrote: > > On 05/25/2011 04:06 AM, Josef Weidendorfer wrote: > > > You need to use callgrind_annotate. > > > cg_annotate is the tool for cachegrind output. > > > > > > The naming is a little bit unfortu