Re: wait_for_file ?? [print via pipes - help testing on Windows?]

[bpabbott]

On Sep 17, 2010, at 04:22 PM, Marco Atzeri <address@hidden> wrote:

--- Ven 17/9/10, bpabbott <address@hidden> ha scritto:

 I have encountered hangs as well. In my case, Octave would hang when a function was called that both existed locally and in the private directory of the calling function. If there were no local m-files, except test_printing.m, then I haven't seen a hang.

no local file except the test_printing.m itself

In each case I've examined, the problem appears to be with Octave's internals (i.e. not a problem with the m-files). Unfortunately, I've not been successful creating an example that reliably demonstrates the problem.

In any event, what m-files do you have locally?

You can test specific devices for specific backends. For example the test eps only ...

test_printing fltk -depsc -debug

octave:1> source test_printing.m
octave:2> test_printing fltk -depsc -debug
backend is fltk
print fltk-epsc  -depsc -debug
epstool command: ' cat > 'fltk-epsc.eps' '
fltk-pipeline: ' cat > 'fltk-epsc.eps' '
panic: Segmentation fault -- stopping myself...
attempting to save variables to `octave-core'...
save to `octave-core' complete
Segmentation fault

It also causes a crash of the X-server.

 

This is not what I would expect. Perhaps I'll have to install Linux via VirtualBox and play with it there. What flavor are you running?

Adding "-debug" will also provide more info. For the command above, I get ...

octave:1> test_printing fltk -depsc -debug

backend is fltk

print fltk-epsc  -depsc -debug

epstool command: ' cat > 'fltk-epsc.eps' '

fltk-pipeline: ' cat > 'fltk-epsc.eps' '

epstool command: 'cat > /var/tmp/oct-RkjJfC.eps ; /sw/bin/epstool --quiet --copy --bbox /var/tmp/oct-RkjJfC.eps 'fltk-epsc-tight.eps'  ; rm /var/tmp/oct-RkjJfCeps '

fltk-pipeline: 'cat > /var/tmp/oct-RkjJfC.eps ; /sw/bin/epstool --quiet --copy --bbox /var/tmp/oct-RkjJfC.eps 'fltk-epsc-tight.eps'  ; rm /var/tmp/oct-RkjJfC.eps '

epstool command: 'cat > /var/tmp/oct-lOmHox.eps ; /sw/bin/epstool --quiet --add-tiff-preview --device tiffg3 --dpi 150 /var/tmp/oct-lOmHox.eps 'fltk-epsc-tiff.eps'  ; rm /var/tmp/oct-lOmHox.eps '

fltk-pipeline: 'cat > /var/tmp/oct-lOmHox.eps ; /sw/bin/epstool --quiet --add-tiff-preview --device tiffg3 --dpi 150 /var/tmp/oct-lOmHox.eps 'fltk-epsc-tiffeps'  ; rm /var/tmp/oct-lOmHox.eps '

The epsc output will produce three files. The normal one, one with a tight bbox and a 3rd with a tiff preview.

If you can't produce eps output, what does the following give you?

__parse_print_opts__ ("test.eps", "-depsc")

Ben

 source test_printing.m
octave:4> __parse_print_opts__ ("test.eps", "-depsc")
error: `__parse_print_opts__' undefined near line 4 column 1

 

My bad. Please try ...

__print_parse_opts__ ("test.eps", "-depsc")

Ben