Bug 124406 - graphviz caller graph only partially drawn (no boxes)
Summary: graphviz caller graph only partially drawn (no boxes)
Alias: None
Product: kcachegrind
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Josef Weidendorfer
Depends on:
Reported: 2006-03-28 10:36 UTC by rgpublic
Modified: 2007-02-04 00:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Screenshot (9.11 KB, image/png)
2006-03-28 14:45 UTC, rgpublic
Kcachegrind output (26.19 KB, image/png)
2006-06-03 19:55 UTC, Maurizio Lattuada
Generated dot file (558 bytes, text/plain)
2006-09-16 21:18 UTC, Diego Elio Pettenò
Dot output (998 bytes, text/plain)
2006-09-16 21:19 UTC, Diego Elio Pettenò

Note You need to log in before you can comment on or make changes to this bug.
Description rgpublic 2006-03-28 10:36:56 UTC
Version:            (using KDE KDE 3.5.1)
Installed from:    Ubuntu Packages

In KCachegrind the graph is only partially drawn. No boxes appear. I've attached a screenshot.
I also have the cachegrind file of course but it's large and I dont think it's of any use because
the problem occurs with any cachegrind file. And strangely - the whole thing (i.e. the same cachegrind file) works on a colleagues PC who is still using Breezy (I'm using Kubuntu Dapper).
Comment 1 rgpublic 2006-03-28 14:45:52 UTC
Created attachment 15334 [details]
Comment 2 Josef Weidendorfer 2006-03-28 15:51:19 UTC
Oh. Seems like a graphviz bug.
Which version of graphviz is this?
Comment 3 rgpublic 2006-03-29 13:54:58 UTC
Graphviz Version: 2.2.1-1sarge1
This version comes with (K)ubuntu Dapper. What's peculiar: This version
also comes with Breezy and works flawlessly there. 
Comment 4 Maurizio Lattuada 2006-06-03 19:55:31 UTC
Created attachment 16454 [details]
Kcachegrind output

This is the cachegrind ouput
Comment 5 Maurizio Lattuada 2006-06-03 19:59:31 UTC
i've the same version of kcachegrind/graphviz of rgpublic@gmx.net
Comment 6 Diego Elio Pettenò 2006-09-15 23:19:16 UTC
Same problem here with KCacheGrind 3.5.4 graphviz 2.8 on Gentoo.
Comment 7 Josef Weidendorfer 2006-09-16 21:04:04 UTC
Can someone of you which sees this bug start KCachegrind from a terminal,
and when a (buggy) graph is drawn, there should be someting like

 kcachegrind: Running 'dot /tmp/kde-weidendo/kcachegrind33hR0b.dot -Tplain'...

shown in the terminal. The given file exists as long as the graph is

Can you please attach (1) the file mentioned as argument to the
shown dot command line, and (2) the stdout of this command when
rerun in the shell? For smaller data, it would be good to choose
a function with a small call graph around.

This way, I at least can check if this is a bug in dot/graphviz
or not.

Comment 8 Diego Elio Pettenò 2006-09-16 21:18:34 UTC
Created attachment 17795 [details]
Generated dot file
Comment 9 Diego Elio Pettenò 2006-09-16 21:19:02 UTC
Created attachment 17796 [details]
Dot output
Comment 10 Josef Weidendorfer 2006-09-16 22:03:33 UTC
Ok ... really strange.
On my Suse 10.1, I get exactly the same dot output as Diego
(I have dot version 2.6), but my graphs show fine here.
So this has nothing to do with dot/graphviz, and yet, I can
not reproduce it.

Perhaps some other runtime environment issue?
What version of GCC, libc, QT are you using?
Comment 11 Diego Elio Pettenò 2006-09-16 22:11:21 UTC
Compiler GCC 4.1.1 (-r1), KDE 3.5.4, Qt 3.3.6 + qtimm patch.

if you can point me toward something to look for, might be an unstated dependency missing, or something similar.
Comment 12 Sebastián Marconi 2007-01-08 15:25:20 UTC
Exactly the same problem here, using the package from kubuntu edgy (6.10) and also compiling it:

dot version 2.8 (Wed Jul 12 21:03:29 UTC 2006)
Qt: 3.3.6
KDE: 3.5.5
KCachegrind: 0.4.6
gcc (GCC) 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)

The output graph it's ok running the command in the terminal, but not in the program. Any idea? 
Comment 13 Sebastián Marconi 2007-01-08 15:47:43 UTC
Here's the output with DEBUG_GRAPH = 1

kcachegrind: Loading /home/k7k0/temp/debug/cachegrind.out.firefoxprofiler ...
kcachegrind: CallGraphView::refresh
kcachegrind: buildGraph(a,0,1) [to Callings]
kcachegrind: buildGraph(d,1,1) [to Callings]
kcachegrind: buildGraph(a,0,1) [to Callers]
kcachegrind: Running 'dot /tmp/kde-k7k0/kcachegrindPRAbma.dot -Tplain'...
kcachegrind: Selected a
kcachegrind: /tmp/kde-k7k0/kcachegrindPRAbma.dot:1 - graph (0 x 2) => (0 x 140)
kcachegrind: /tmp/kde-k7k0/kcachegrindPRAbma.dot:2 - node 'F8303ae8' ( 0/0 - 0x0 ) => (626/552 - 0x0)
kcachegrind: /tmp/kde-k7k0/kcachegrindPRAbma.dot:3 - node 'F8303eb8' ( 0/1 - 0x0 ) => (626/482 - 0x0)

Here's the callgrind file:
version: 0.9.6
cmd: file:/home/k7k0/proyectos/profiler/firefoxprofiler
part: 1

events: Time

3 171

19 6

15 5

5 4

10 25
calls=1 0
5 4

23 140
calls=1 0
19 6
calls=1 0
15 5
calls=1 0
10 25
Comment 14 Albert Astals Cid 2007-02-04 00:24:26 UTC
Just fixed that bug. It will be there on KDE 3.5.7 (if exists) or KDE4 otherwise.