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

[Michael D. Godfrey]

On 09/17/2010 11:48 AM, bpabbott wrote:

You can do things like ...

test_printing fltk -dpng -debug

... this will only produce png output for the fltk backend, and will display information regarding any system commands used for the pipes. If you encounter a hang, just ctrl-C and try again.

octave:1> test_printing fltk -dpng -debug

backend is fltk

print fltk-png  -dpng -debug

Ghostscript command: '/sw/bin/gs -dQUIET -dNOPAUSE -dBATCH -dSAFER -sDEVICE=png16m -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r150x150 -dEPSCrop -sOutputFile=fltk-png.png -'

fltk-pipeline: '/sw/bin/gs -dQUIET -dNOPAUSE -dBATCH -dSAFER -sDEVICE=png16m -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r150x150 -dEPSCrop -sOutputFile=fltk-png.png -'

octave:2> 

If you do encounter a hang, make sure there are no m-files in your pwd with the same name as those in ...scripts/plot/...

I don't know why local copies cause Octave to hang for me, but the good news is that I only get one hang per session.

Ben

Basically, no.  All print commands using fltk produce the same seg fault:
octave:1> test_printing fltk -dpng -debug
Xlib:  extension "NV-GLX" missing on display ":1175.0".
backend is fltk
print fltk-png  -dpng -debug
Ghostscript command: '/usr/bin/gs -dQUIET -dNOPAUSE -dBATCH -dSAFER -sDEVICE=png16m -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r150x150 -dEPSCrop -sOutputFile=fltk-png.png -'
fltk-pipeline: '/usr/bin/gs -dQUIET -dNOPAUSE -dBATCH -dSAFER -sDEVICE=png16m -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r150x150 -dEPSCrop -sOutputFile=fltk-png.png -'
GL2PS error: Bad file pointer
panic: Segmentation fault -- stopping myself...
attempting to save variables to `octave-core'...
save to `octave-core' complete
Segmentation fault (core dumped)
=============================

The gdb bt output some an example case is attached.

Michael

gdb_test01
Description: Text document