From bug-octave-request at bevo dot che dot wisc dot edu  Wed Jan 20 11:25:51 1999
Subject: Unidentified subject!
From: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
To: Dan E Kelley <kelley at Intrusion dot Phys dot Ocean dot Dal dot CA>
Cc: bug-octave at bevo dot che dot wisc dot edu
Date: Wed, 20 Jan 1999 11:25:24 -0600 (CST)

On 20-Jan-1999, Dan E Kelley <kelley at Intrusion dot Phys dot Ocean dot Dal dot CA> wrote:

| To: bug-octave at bevo dot che dot wisc dot edu
| Cc: kelley
| Subject: octave immediately seg-faults
| 
| Bug report for Octave 2.0.13 configured for i686-pc-linux-gnulibc1
| 
| Description:
| -----------
| 
| I'm quite keen to get octave working on my linux machine, since it
| seems like a great program!
| 
| However, running octave immediately generates segfaults, with message:
| 
| 	error: Segmentation fault -- stopping myself...
| 	error: attempted clean up apparently failed -- aborting...
| 	Aborted (core dumped)
| 
| The debugger indicates:
| 
| 	gdb) where
| 	#0  0x4040186a in malloc ()
| 	#1  0x4045ed88 in __DTOR_END__ ()
| 	#2  0x4045d6a8 in __morecore ()
| 	#3  0x55000000 in ?? ()
| 	Cannot access memory at address 0x26b48d.
| 
| I can do further tests if instructed.  Thanks in advance for any help!

Problems like this on Linux systems are almost always due to
incompatible C and C++ library versons, or because the C++ header
files don't match the installed copy of the C++ library.

jwe