Solaris 10 5/08 Octave segfault

[John W. Eaton]

On 23-Jul-2008, Sergei Steshenko wrote:

| > > --- On Wed, 7/23/08, John Wiggins
| > <jwiggins at rutgers.edu> wrote:
| > >
| > >   
| > >> From: John Wiggins <jwiggins at rutgers.edu>
| > >> Subject: Solaris 10 5/08 Octave segfault
| > >> To: bug-octave at octave.org
| > >> Date: Wednesday, July 23, 2008, 12:45 PM
| > >> Hi,
| > >>
| > >> I just built octave-3.0.1 on Solaris 10 5/08
| > sparc, but it
| > >> segfaults on 
| > >> startup:
| > >>
| > >> truss /usr/local/bin/octave-3.0.1
| > >>
| > >> ...
| > >> .
| > >> ..
| > >> ..
| > >> open64("/var/run/name_service_door",
| > O_RDONLY)  =
| > >> 4
| > >> fcntl(4, F_SETFD, 0x00000001)                   =
| > 0
| > >> door_info(4, 0xFCBF1688)                        =
| > 0
| > >> door_call(4, 0xFFBFF060)                        =
| > 0
| > >> sysinfo(SI_HOSTNAME, "clean", 255)      
| >        =
| > >> 6
| > >>     Incurred fault #6, FLTBOUNDS  %pc = 0xFCCB1A20
| > >>       siginfo: SIGSEGV SEGV_MAPERR addr=0xFFFFFFF4
| > >>     Received signal #11, SIGSEGV [default]I
| > >>       siginfo: SIGSEGV SEGV_MAPERR addr=0xFFFFFFF4
| > >>
| > >>
| > >> I built things with gcc/gfortran 4.3.1, 32-bit.
| > >>
| > >> Any ideas?

I think this problem might be the same as was discussed in this
message:

  https://www-old.cae.wisc.edu/pipermail/bug-octave/2008-August/006462.html

I think the key fix is the change to file_ops::is_dir_sep.  Depending
on what version of find you have installed on your system, you may
also need the fix in the attachment if you want to be able to use the
run-octave script to run Octave in the build directory.

jwe