Il giorno mar 13 nov 2018, 09:20 John W. Eaton <address@hidden
> ha scritto:
If you use all the same options except the --eval "CODE" part, then
execute the interpimages function call, does that work?
Similarly, but without the --gui option (so you start with a command
For me that does work but then, when I exit Octave I get the segfault.
The qt toolkit should still be registered and should work
as long as you are not using the -cli option for run-octave.
Being a big more methodical this time. I have a shell script file …
./run-octave --gui --norc --silent --no-history --path /Users/bpabbott/Development/mercurial/default/sources/doc/interpreter/ --eval "interpimages ('doc/interpreter/', 'interpn', 'txt');"
This seg-faults. I’ve tried to run the gui manually (i.e. no —path or —eval options). Something changed for the gui. Readline looks to be not working and fputs is throwing errors. I’ll look into these first.
The readline trouble went away after I pull, update, make.
Running gui, then plotting, and existing produces the seg-fault.
I must have made a mistake earlier.