help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with Print under Octave 3.8.1 under windows


From: Andreas Weber
Subject: Re: Problem with Print under Octave 3.8.1 under windows
Date: Sat, 14 Jun 2014 14:32:08 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.5.0

Am 14.06.2014 02:09, schrieb ijourneaux:
> I started to install Octave 3.8.1 on a new computer and I am getting the
> following error message. This same install pack works on an other computer
> so I am not sure what the problem might be.  I tried reinstalling Octave and
> GhostScript to no avail.  A search of the forum indicates the problem has
> occurred with others but I was unable to locate a solution
> 
>>> x = -10:0.1:10;
>>> plot (x, sin (x));
>>> print ('-dpng','test.png')
> warning: print.m: epstool binary is not available.
> Some output formats are not available.
> Error: /undefined in -1.#IND
> Operand stack:
>    --nostringval--
> Execution stack:
>    %interp_exit   .runexec2   --nostringval--   --nostringval--  
> --nostringval
> --   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--
> false   1   %stopped_push   1950   1   3   %oparray_pop   1949   1   3  
> %oparr
> ay_pop   --nostringval--   1933   1   3   %oparray_pop   1819   1   3  
> %oparra
> y_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--  
> --nost
> ringval--   --nostringval--   2   %stopped_push   --nostringval--
> Dictionary stack:
>    --dict:1189/1684(ro)(G)--   --dict:0/20(G)--   --dict:82/200(L)--  
> --dict:4
> 0/64(L)--
> Current allocation mode is local
> Last OS error: No such file or directory
> GPL Ghostscript 9.14: Unrecoverable error, exit code 1
>>> print ('-dpng','test.png')

Are you using fltk or gnuplot as graphics_toolkit?
You could also add "-debug" to your print command (for example
print("testplot.ps","-debug") to see the gnuplot or fltk pipeline.
In the case of gnuplot you'll also find a octave-print-commands.log
which might help finding the problem (if it also exists with gnuplot).

Another way to find the problem is to save as ps or eps and run then gs
from the commandline without QUIET (perhaps there is also a verbose flag)

-- Andy

PS: I want to create a wiki page "debug plotting issues in octave",
would you like to help me?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]