Graphviz Issue Tracker
Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0002046graphvizDotpublic2011-02-09 04:472011-04-28 04:03
ReporterAnders Lindblad 
Assigned Togviz 
PrioritynormalSeveritymajorReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOSx86-Linux-Suse SLES 10OS Version
Summary0002046: Problem with graph parser
Description



As seen from the excerpt below, dot has a problem.
Unfortunately, I can not disclose dottybug.dot file.
What does problem: gvwrite_no_z mean 115?
Testing with another inputfile resulted in
problem: gvwrite_no_z problem 452
What does this message mean?
   Thanks,



    Anders



<CD>
=======================================================================
dotty version 96c (09-24-96)
lefty version 10 Mar 2005
graphviz version 2.26.3 (20100126.1600)






egypt ricDeviceCtrlTest.cc.104r.expand | dotty -
graph parser: syntax error near line 275
context: >>> This <<< is done by .my_tcshrc_basic
Error: gvwrite_no_z problem 115
dotty.lefty: giving up on dot
dotty.lefty: graph that causes dot
dotty.lefty: to fail has been saved in file dottybug.dot
dotty.lefty: please fill out a bug report at
dotty.lefty: http://www.graphviz.org/bugs/bugform.html [^]
Error: gvwrite_no_z problem 115
</CD>
Additional Information

Please keep this problem report private.

    Thanks,

    Anders

[ellson]
Somewhere in the graph file that you can't share with us, you have a
line that contains:

    This is done by .my_tcshrc_basic

Which, I'd guess, is not properly commented (use /*...*/ or // )

The "gvwrite_no_z problem 115" message some kind of problem during the
writing of a compressed string.

What -T output format are you using?

[erg]

Since he is using dotty, it is probably getting -Txdot.

Before using dotty, just run your output through dot.

   egypt ricDeviceCtrlTest.cc.104r.expand | dot > out

This will be a simpler way to clean up syntax errors than
having to go though dot and dotty.

[anders]
I'd already thought of making the .my_tcshrc_basic,
which of course is the normal mode of operation,
but due to recent environmental problems it happened
to be non-verbose.

Then regarding your question about output format, I don't know
which one of the tools you refer to?

Which would be the preferred format?

[anders]
Your suggestion worked fine.
Now I just need to figure how to tailor the input.
The first result of using -Tps showed up in ghostviev as a
piece of black clutter in one end of the paper.
Nice thing though is that when didn't use dotty but
dot directly I got a result that I can process further.

TagsNo tags attached.
AUXILLARY-FILES
DATE-FIXED
FIX-COMMENT
FORMER-ID2132
INPUT-FILE
OUTPUT-FILE
STATUS-COMMENT*
VERSION     2.26.3
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2011-04-28 04:03 user1 New Issue
2011-04-28 04:03 user1 Assigned To => user1


MantisBT 1.2.5[^]
Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker