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

[Markus Mützel]

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

The POSIX documentation for "exec" states:
https://man7.org/linux/man-pages/man3/exec.3.html
>        The exec() family of functions replaces the current process image
>        with a new process image.

IIUC, that means that the Octave process is replaced by the new process. That
means that Octave stops executing as the other process starts.
It looks like this is happening on Windows 10. I don't see any error message
(with CLI or with GUI).

If I attach gdb to Octave 6.2.0 and run an "exec" command, I see:

[Inferior 1 (process 11780) exited normally]
(gdb)


It looks like the segfault on exit has been fixed some time on the way.

Closing report.


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/