Re: Segmentation Fault with Octave MXE under Windows

[ijourneaux]

>> Type "bt" inside gdb to get an actual stack trace. 
>> Also, can you compile MXE without optmisation? 
>> Jordi G. H. 

Here is the back trace
#0  0x68a807c0 in liboctinterp-2!_ZN5ArrayIdED2Ev ()
   from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll
#1  0x689e19fc in liboctinterp-2!_ZN13octave_matrixD0Ev ()
   from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll
#2  0x68a7164a in liboctinterp-2!_ZN5ArrayI12octave_valueED2Ev ()
   from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll
#3  0x689cd496 in liboctinterp-2!_ZN10octave_mapD1Ev ()
   from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll
#4  0x689ea285 in liboctinterp-2!_ZN13octave_structD0Ev ()
   from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll
#5  0x68b4bd89 in
liboctinterp-2!_ZNSt8_Rb_treeISsSt4pairIKSs12octave_valueESt10
_Select1stIS3_ESt4lessISsESaIS3_EE8_M_eraseEPSt13_Rb_tree_nodeIS3_E ()
   from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll
#6  0x684a7bbe in liboctinterp-2!_ZN20octave_user_functionD2Ev ()
   from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll
#7  0x684a7e7b in liboctinterp-2!_ZN20octave_user_functionD0Ev ()
   from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll
#8  0x688962a9 in liboctinterp-2!_Z4FsylRK17octave_value_listi ()
   from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll
#9  0x689da93f in liboctinterp-2!_ZN12symbol_table9clear_allEb ()
   from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll
#10 0x6889bf74 in liboctinterp-2!_ZN12symbol_table7cleanupEv ()
   from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll
#11 0x688da55b in liboctinterp-2!_Z9main_loopv ()
   from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll
#12 0x688dbe52 in liboctinterp-2!_Z17clean_up_and_exitib ()
   from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll
#13 0x680c513c in octave_execute_interpreter ()
   from C:\Octave\Octave-3.8.1\bin\liboctinterp-2.dll
#14 0x00402935 in ?? ()
#15 0x004013e2 in ?? ()
#16 0x75f9ee1c in KERNEL32!BaseThreadInitThunk ()
   from C:\Windows\system32\kernel32.dll
#17 0x76e137eb in ntdll!RtlInitializeExceptionChain ()
   from C:\Windows\system32\ntdll.dll
#18 0x76e137be in ntdll!RtlInitializeExceptionChain ()
   from C:\Windows\system32\ntdll.dll
#19 0x00000000 in ?? ()

When I copy over that has the symbols I get this additional information.

#0  Array<double>::~Array (this=0x1ff22200, __in_chrg=<optimized out>) 
    at
/mxe-octave/tmp-stable-octave/octave-3.8.1/liboctave/array/Array.h:243 
243     in
/mxe-octave/tmp-stable-octave/octave-3.8.1/liboctave/array/Array.h 

Unfortunately it seems that with MXE, some of the files needed for debugging
are not available.

Turning off optimization is a great idea.  Just to make sure, would this
require removing the CFLAGS='O2' and CXXFLAGS='O2' from the makefile? Is
there a better place to make the change?

    HOST_AND_BUILD_CONFIGURE_OPTIONS := \
            CC='$(MXE_CC)' CXX='$(MXE_CXX)' F77='$(MXE_F77)'
DLLTOOL='$(MXE_DLLTOOL)' CCAS='$(MXE_CCAS)' \
            CFLAGS='-O2' CXXFLAGS='-O2' ac_cv_f77_compiler_gnu=no
RANLIB='$(MXE_RANLIB)'





--
View this message in context: 
http://octave.1599824.n4.nabble.com/Segmentation-Fault-with-Octave-MXE-under-Windows-tp4664305p4664345.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.