Re: Running under MacOsX 10.5

[Ben Abbott]

On Jul 18, 2012, at 12:17 PM, CdeMills wrote:

> Hello,
> 
> I'm trying to run octave on a Intel based Mac running MacOSX 10.5. What I
> did:
> 1) install the macport system
> 2) install gcc-4.7
> 3) compiled all octave dependencies with gcc47, using compiler flags '-O3
> -ftree-vectorize'
> 4) compiled octave 3.6.2 the same way
> 
> MacOSX 10.5 core libs are compiled using 32 bits instructions; yet the
> system seems to run programs compiled with 64 bits instruction without
> problem. During the compile process, I didn't mess with the architecture
> (Programs can be compiled to be executed under 32 bit or 64 bits
> environment; the so-called "universal" model).
> 
> 'make check' hangs after the first batch of tests with:
> 
> terminate called after throwing an instance of 'octave_interrupt_exception'
> panic: Abort trap -- stopping myself...
> attempting to save variables to `octave-core'...
> save to `octave-core' complete
> 
> I tried: ./run-octave -g
> (gdb) catch catch
> (gdb) run
> ( a lot of messages about loaded libs; then .octaverc is executed)
> octave:1> exit
> Cannot access memory at address 0xffffffd0
> 
> Catchpoint 1 (exception caught).
> Catchpoint 1 (exception caught), throw location unknown, catch location
> unknown, exception type unknown
> 0x0466a1f0 in __cxa_begin_catch ()
> 
> flags were set as
> 
>  CXXFLAGS="-pipe -O3 -ftree-vectorize -g -ggdb3" \
>        FFLAGS="$CXXFLAGS -D_THREAD_SAFE -pthread -gstabs" \
>        CFLAGS="$FFLAGS -lstdc++" \
> 
> so debugging info should be present. How can I locate the place where the
> exception occurs ?
> 
> TIA
> 
> Pascal

Pascal,

Assuming you've build Octave with the debugging information included (I add 
"-g" to CXXFLAGS, CFLAGS, and FFLAGS) then "./run-octave -g" and when you 
encounter the crash, type "bt" for the back-trace.

Ben