Re: Troubleshooting segmentation Violation Octave MXE 3.8.0 Win7 32bit

[Philip Nienhuis]

ijourneaux wrote
> I am trying to troubleshoot a segmentation violation error under Octave
> 3.8.0 MXE Win7 32bit.
> 
> The segmentation violation appears after my script successfully completes
> when I exit Octave. The simplest example I can come up with is
> 
> AI3c1=imread('AI3c70.tif');
> AI3cr=imrotate(AI3c1,5,'nearest','crop');
> 
> This completes successfully but crashes when I exit Octave.
> 
> Any thoughts on how I can troubleshoot further? Perhaps the only recourse
> is to build a system where I can build Octave from scratch.
> 
> Here is the link to the image.
> https://dl.dropboxusercontent.com/u/76158792/AI3c70.tif

Probably no comfort (sorry):
This also segfaults in octave-3.8.1-rc4 (cross-built w. MXE) with
image-2.2.0 package (CLI and GUI).

A backtrace from gdb yields (after final Ctrl-d as per your instructions):

Program received signal SIGSEGV, Segmentation fault.
0x6886ba20 in liboctinterp-2!_ZN5ArrayIdED2Ev ()
   from c:\octave\octave-3.8.1-rc4\bin\liboctinterp-2.dll
(gdb) bt
#0  0x6886ba20 in liboctinterp-2!_ZN5ArrayIdED2Ev ()
   from c:\octave\octave-3.8.1-rc4\bin\liboctinterp-2.dll
#1  0x687d6fc6 in liboctinterp-2!_ZN13octave_matrixD0Ev ()
   from c:\octave\octave-3.8.1-rc4\bin\liboctinterp-2.dll
#2  0x6885c862 in liboctinterp-2!_ZN5ArrayI12octave_valueED2Ev ()
   from c:\octave\octave-3.8.1-rc4\bin\liboctinterp-2.dll
#3  0x687c7dc6 in liboctinterp-2!_ZN10octave_mapD1Ev ()
   from c:\octave\octave-3.8.1-rc4\bin\liboctinterp-2.dll
#4  0x687ded45 in liboctinterp-2!_ZN13octave_structD0Ev ()
   from c:\octave\octave-3.8.1-rc4\bin\liboctinterp-2.dll
#5  0x6891c811 in
liboctinterp-2!_ZNSt8_Rb_treeISsSt4pairIKSs12octave_valueESt10_Select1stIS3_ESt4lessISsESaIS3_EE8_M_eraseEPSt13_Rb_tree_nodeIS3_E
()
   from c:\octave\octave-3.8.1-rc4\bin\liboctinterp-2.dll
#6  0x683ba410 in liboctinterp-2!_ZN20octave_user_functionD2Ev ()
   from c:\octave\octave-3.8.1-rc4\bin\liboctinterp-2.dll
#7  0x683ba65b in liboctinterp-2!_ZN20octave_user_functionD0Ev ()
   from c:\octave\octave-3.8.1-rc4\bin\liboctinterp-2.dll
#8  0x686c914b in liboctinterp-2!_Z4FsylRK17octave_value_listi ()
   from c:\octave\octave-3.8.1-rc4\bin\liboctinterp-2.dll
#9  0x686ce0bb in liboctinterp-2!_ZN12symbol_table7cleanupEv ()
   from c:\octave\octave-3.8.1-rc4\bin\liboctinterp-2.dll
#10 0x686fb05a in liboctinterp-2!_Z9main_loopv ()
   from c:\octave\octave-3.8.1-rc4\bin\liboctinterp-2.dll
#11 0x686fc663 in liboctinterp-2!_Z17clean_up_and_exitib ()
   from c:\octave\octave-3.8.1-rc4\bin\liboctinterp-2.dll
#12 0x680c4faf in octave_execute_interpreter ()
   from c:\octave\octave-3.8.1-rc4\bin\liboctinterp-2.dll
#13 0x00401d15 in octave-cli!main ()
(gdb)

...but I if I'm not mistaken the mxe-built octave executable has been
stripped (from debug symbols).
I have very little time these weeks, but maybe another mxe build w/o
stripping Octave & dependencies is easy to do (I think I saw such an option
in the mxe configure help).
Note that even with a (perhaps) better backtrace I cannot do much - I'm
actually a C++ n00b. Other devs need to help out here.

Philip




--
View this message in context: 
http://octave.1599824.n4.nabble.com/Troubleshooting-segmentation-Violation-Octave-MXE-3-8-0-Win7-32bit-tp4662643p4662650.html
Sent from the Octave - General mailing list archive at Nabble.com.