Solaris 10 x86 compilation success leads to 2.9.13 "octave" core, segmentation violation. :-<.....

[John W. Eaton]

On 28-Aug-2007, John wrote:

| I installed GNU gcc 3.4.3, from source, and stripped out LD references 
| to its fortran libraries. Eventually, I was able to successfully compile 
| static and dynamic builds of "octave". Unfortunately, per dbx, there is 
| a segmentation violation, and a core file:
| 
| bash-3.00$ dbx /home/arthur/bin/octave core
| For information about new features see `help changes'
| To remove this message, put `dbxenv suppress_startup_message 7.4' in 
| your .dbxrc
| Reading octave
| core file header read successfully
| Reading ld.so.1
| Reading liboctinterp.so.2.9.13
| Reading liboctave.so.2.9.13
| Reading libcruft.so.2.9.13
| Reading libreadline.so.5
| Reading libncurses.so.5.5
| Reading libdl.so.1
| Reading libg2c.so.0.0.0
| Reading libm.so.2
| Reading libgcc_s.so.1
| Reading libstdc++.so.6.0.3
| Reading libc.so.1
| program terminated by signal SEGV (no mapping at the fault address)
| Current function is std::basic_string < char, std::char_traits<char>, 
| std::allocator<char> >::find
|   269         { return &((reinterpret_cast<_Rep*> (_M_data()))[-1]); }
| (dbx) where

I doubt that this is a bug in Octave.  It looks similar to the Cygwin
GCC bug discussed here:

  http://www.cygwin.com/ml/cygwin/2005-10/msg00051.html

jwe