Marius Mikucionis wrote:
Package: graphviz
Version: 2.2.1-1
Severity: important
Not sure whether it is connected to 305375, but I don't know how to work
arround the segfault, it's very anoying and I can't work with it.
obviously there is memory mishandling somewhere.
valgrind can locate the illegal segment read in the code, it should be easy to
find and fix with debug info built in.
I attach the dot file, verbose dot output and valgrind output.
The bug is reproducable via command line:
dot -Tps -ocompressor.ps compressor.dot
(I tried different formats, but it breaks no matter which).
thanks!
We tried this here (upstream) with 2.2.1 on i686, and with latest CVS on
x86_64,
and we don't get the segfault but we do get:
$ dot compressor.dot >/dev/null
Error: lost IUT_ActionHandler ENV_Action edge
Error: lost IUT_ActionHandler ENV_Action edge
Error: lost IUT_ActionHandler ENV_Action edge
So we're not completely innocent, but perhaps the segfault is debian
specific?
John
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
