Re: Octave Installer for Windows with Debug Option

[Markus Mützel]

Again: Please use bottom or interleaved posting when writing to this mailing 
list!

Am 09. Juni 2020 um 11:23 Uhr schrieb "Stefan Pofahl":
> Ok Markus,
> 
> sorry for my mistake, I thought "cmdshell.bat" is more or less the same as 
> "cmd.exe",
> I was not aware of this batch-file.
> Here is the new output:
> -------------------------------------------------------------------------------------------------------
> Reading symbols from C:\Octave\OCTAVE~1.0\mingw64\bin\octave-gui.exe...
> (No debugging symbols found in 
> C:\Octave\OCTAVE~1.0\mingw64\bin\octave-gui.exe)
> (gdb) c
> Continuing.
> [Thread 14828.0x2920 exited with code 0]
> [Thread 14828.0xc2c exited with code 0]
> 
> Thread 24 received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 14828.0x3c1c]
> 0x00007ffe236015f9 in ucrtbase!_wcreat () from 
> C:\WINDOWS\System32\ucrtbase.dll
> (gdb) tb
> Temporary breakpoint 1 at 0x7ffe236015f9
> (gdb)
> -------------------------------------------------------------------------------------------------------------
>

Well, this is tedious...
Please, do that again and request the backtrace with "bt" (not "tb"!)...
 
> You wrote:
> > If the problem only occurs on Ubuntu, why the trouble to debug on Windows?
>  
> It is the opposit, it crashes only in "octave-gui.exe"

This is not what you wrote in your previous message...

Markus