|Anonymous | Login||2017-11-18 08:42 EST|
|Main | My View | View Issues | Change Log | Roadmap | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001496||graphviz||Dot||public||2008-12-04 03:48||2011-04-28 04:03|
|Assigned To||Arif Bilgin|
|Platform||OS||x86-Windows-Vista 32-bit||OS Version|
|Summary||0001496: Graphviz cannot be run from another directory on windows|
(The Installer is versioned 2.20.3, latest stable as of 2008-12-03, but the directory created was 'Graphviz 2.21'.)
* Install graphviz - works fine
* Copy the Graphviz directory to another place, like c:\temp\graphviz
* command prompt - cd to c:\temp\graphviz\bin
* run 'dot'
* the following error appears:
Assertion failed: v, file input.c, line 324
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Moving and re-zipping the graphiviz dir was possible previously (last year or so), and is
important for us in order simplify distribution & version control among developers & build slaves.
It makes graphviz a bit unusable for us at the moment. :(
Some comments on the current state & solutions:
* Requiring an install makes things unnessary complex.
* Requiring the exakt same directory layout is fine.
* Having an optional env-var called GRAPHVIZ_DIR that can be used to denote
the desired graphviz dir would be an acceptable workaround.
Thanks for making and maintaining such an excellent tool!
[Sylvain Soliman] Bug 1533 seems to be related to a missing "config" file for dot.exe,
copying it along seems to solve the problem. However it is true that the
error message is at least misleading... (dot could instead create the file
if found missing...).
A normal user running dot doesn't have sufficient permission to create the config file.
"dot -c" needs to be run during the install process when the "user" has permission to
write into the library directory.
At least, that is the way it was designed to work on 'nix systems.
Well, then at least the error message should tell that "config" was not
found, instead of the obscure "Assertion failed..." message. This way the
user who reported the original bug might have solved it easily (and I would
have solved it more quickly
I definitely agree with that.
In fact we discussed that recently.
[ellson] fair enough. The change is in CVS and should be in tomorrow's development snapshot.
Great! Thanks for the fast response. I guess bug 1533 can be marked as
|Tags||No tags attached.|
|STATUS-COMMENT||Fixed (6 Feb 2009)|
|2011-04-28 04:03||user1||New Issue|
|2011-04-28 04:03||user1||Assigned To||=> Arif Bilgin|
|MantisBT 1.2.5[^] Copyright © 2000 - 2011 MantisBT Group|