Re: Octave Installer for Windows with Debug Option

[Stefan Pofahl]

Something more, after I hit two times more: "c" and than "tb" again. (see attached txt)

Am Di., 9. Juni 2020 um 11:23 Uhr schrieb Stefan Pofahl <stefan@pofahl.de>:

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)

-------------------------------------------------------------------------------------------------------------

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"

Regards,

Stefan

Am Di., 9. Juni 2020 um 10:45 Uhr schrieb Markus Mützel <markus.muetzel@gmx.de>:

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
  

--

Stefan Pofahl
Zollgasse 5
8020 Graz
Österreich
Tel.: +43 (316) 33 2001

--

Stefan Pofahl
Zollgasse 5
8020 Graz
Österreich
Tel.: +43 (316) 33 2001

dbg_output_in_cmdshell.txt
Description: Text document