[pstricks] linestyle=dashed problems with ps2pdf

[Antoine Pairet]

On Mon, 2010-04-05 at 17:14 +0200, Herbert Voss wrote:
> Am 05.04.2010 16:35, schrieb Antoine Pairet:
> > gives me this error:
> > ! Undefined control sequence.
> > \pst@@@vlabel ... \psk at ylogBase \@empty \psvlabel 
> >                                                   {\expandafter
> > \@LabelComma...
> > l.6 ...graph}{->}(5.2,-3)(5.2,-3)(5.8,0){9cm}{5cm}
> 
> you have to update pst-plot and pst-node, which now
> provide most of the extensions of pstricks-add

Thanks,
After upgrading from
pst-plot.tex    2010/02/11 1.10 `pst-plot' (tvz,hv)
to
pst-plot.tex    2010/03/15 1.11 `pst-plot' (tvz,hv)
the problem was solved!

I have another problem which is not related to the previous one. When
using the the option linestyle=dashed, the code compiles fine, however,
the conversion from PS to PDF fails. The compilation scheme is this one:
1. latex test.tex
2. dvips test.dvi
3. ps2pdf test.ps

latex and dvips run fine, but ps2pdf gives an error:
Error: /stackunderflow in --exch--
Operand stack:
   y1
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--
--nostringval--   false   1   %stopped_push   1862   1   3   %
oparray_pop   1861   1   3   %oparray_pop   1845   1   3   %oparray_pop
1739   1   3   %oparray_pop   --nostringval--   %
errorexec_pop   .runexec2   --nostringval--   --nostringval--
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--
--nostringval--
Dictionary stack:
   --dict:1154/1684(ro)(G)--   --dict:0/20(G)--   --dict:112/200(L)--
--dict:169/300(L)--   --dict:38/200(L)--   --dict:107/200(L)--
Current allocation mode is local
Last OS error: 2
Current file position is 102111
GPL Ghostscript 8.70: Unrecoverable error, exit code 1


Minimal example:
\documentclass{minimal}
  \usepackage{pstricks-add}
  \listfiles
\begin{document}
\begin{pspicture}(1,1)
  \psline[linestyle=dashed](0,0)(1,1)
\end{pspicture}
\end{document}

Could the problem come from outdated files? and more precisely .pro
files? Which .pro files should I upgrade?

Best regards,
Antoine