[Octave-bug-tracker] [bug #63809] Octave GUI Crashing When Opening on Windows 11

[anonymous]

Follow-up Comment #41, bug #63809 (project octave):

Since I yesterday performed Windows 10 update I have the very same issue, CLI
works so does plotting, but GUI doesn't, throws out a white window for a
moment and closes then.
Running GUI from gdb:

Browse to the folder where Octave is installed and open the shell by
double-clicking the cmdshell.bat script.
At the prompt, type gdb octave. That should start gdb attached to the octave
executable.
At the (gdb) prompt, type r --gui. That should start Octave in GUI mode.

gives exactly the same that was already reported

(gdb) r --gui
Starting program: C:\Octave\Octave-7.3.0\mingw64\bin\octave.exe --gui
[New Thread 7968.0x43c]
[New Thread 7968.0xd58]
[New Thread 7968.0x3e68]
C:\Octave\Octave-7.3.0\mingw64\bin\octave.exe: No error
[Thread 7968.0x3e68 exited with code 3221225477]
[Thread 7968.0x43c exited with code 3221225477]
[Thread 7968.0xd58 exited with code 3221225477]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.


    _______________________________________________________

Reply to this item at:

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

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