Re: Octave Installer for Windows with Debug Option

[Markus Mützel]

Please, use bottom or interleaved posting when writing to this mailing list.

Am 09. Juni 2020 um 10:10 Uhr schrieb "Stefan Pofahl":
> Hi Markus,
>  
> thanks for the hint to move first to the directory where "octave-gui.exe" is 
> located before starting
> dbg.
> I followed exactly your procedure.
> And I followed an automated procedure.
> Both give the same result.
> Here my automated procedure to start gdb.exe
> ------------------------------------------------------------------------------------
> DIR_octave_gui = 'C:\Octave\Octave-5.2.0\mingw64\bin';
> if exist(DIR_octave_gui, 'dir')
>     cd(DIR_octave_gui);
>     pwd
> end
> if ispc
>     % windows:
>     % cmd.exe /c start "" "C:\Octave\Octave-5.2.0\mingw64\bin\gdb.exe" -p 
> petpid
>     s_cmd = sprintf( "cmd.exe /c start \"gdb\" 
> \"C:\\Octave\\Octave-5.2.0\\mingw64\\bin\\gdb.exe\" -p %d", getpid() );
>     system(s_cmd);
> else
>     % unix/linux:
>     system(sprintf("gnome-terminal --command 'gdb -p %d'", getpid()), 
> "async");
> end
> ------------------------------------------------------------------------------------
>

Don't use "cmd.exe" but the "cmdshell.bat" in the directory where Octave is 
installed (*not* the directory where "octave-gui.exe" is!).
It's possible, the environment for gdb isn't set up correctly if you use 
"cmd.exe".
 
> I know exactly where it crashes, it is a function provided by python: 
> Py_Initialize();
> To provoke the crash I gave the command:
> octave> pycall("sysconfig.get_python_version");
> 
> This command is nested inside "pyversion.m".
> 
> And this causes troubles only in the octave-gui.exe on Ubuntu and inside 
> octave-cli everything
> works fine. And it does not always crash, it crashes at least in 90% of the 
> time. 

If the problem only occurs on Ubuntu, why the trouble to debug on Windows?

> Attached the screen output from gdb.exe.
> 

If you don't get a backtrace, Octave with symbols would not be any more helpful.

Markus