[Octave-bug-tracker] [bug #47840] exec segfaults on Windows

[Nicholas Jankowski]

Follow-up Comment #1, bug #47840 (project octave):

Just to add to the data set:

Running 4.0.1 on Windows 7 (installed from zip file, not exe installer)

running exec("ls","-l") from octave gui  closes Octave.  after some time a
message appears 


octave-gui.exe has stopped working

A problem caused the program to stop working correctly. Please close the
program.

[CLOSE THE PROGRAM] (button)


wondering if it would be different if a command was executed that should wait
for user input, I tried:


>> exec("pause")
ans = -1


no window or anything appears. 

wondering if passing the argument was involved:


>> exec("pause", "-h")
ans = -1


running octave-cli after starting from a windows CMD shell, I get the same
behavior. the only difference is the error message indicates octave-cli.exe
has crashed. then it drops be back to the shell command line.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47840>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/