Timeline for Interpreting callgrind data
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 24, 2018 at 7:55 | comment | added | Wodin |
@nmz787 yes you need to specify the type. e.g. dot -Tsvg dotfile.dot -o graphfile.svg. You can also use pdf or png amongst others.
|
|
| Oct 24, 2017 at 19:27 | comment | added | nmz787 |
are we supposed to actually type in the -T<type> ? or do we replace <type> with something?
|
|
| Sep 20, 2015 at 14:06 | history | edited | Matthieu M. | CC BY-SA 3.0 |
deleted 11 characters in body
|
| Feb 17, 2012 at 16:00 | vote | accept | maverik | ||
| Feb 15, 2012 at 14:44 | comment | added | maverik |
The deal is that actually I need to compare two graphs from two different versions of software, so there is no aim to read/understand the whole graph, I need only some paths and I know where I should look for them. OTOH, generation png image takes about 5 minutes on my Core i7-2600 3.4GHz / 8 Gb DDR3 an resulting file's size is 23 MBytes. Not all image viewers can handle it fast and correctly (perfect stress-test IMO :) )
|
|
| Feb 15, 2012 at 11:22 | comment | added | Frank Osterfeld | Interesting. Is the generated graph readable for 1500 functions? | |
| Feb 15, 2012 at 9:29 | history | answered | maverik | CC BY-SA 3.0 |