From owner-bug-octave at bevo dot che dot wisc dot edu Mon Oct 28 02:21:17 1996 Subject: [50 character or so descriptive subject here (for reference)] From: Randy Gobbel To: bug-octave at che dot utexas dot edu Date: Mon, 28 Oct 1996 00:21:01 -0800 To: bug-octave at che dot utexas dot edu Subject: octave dies w/ segmentation fault when starting Bug report for Octave 1.1.1 configured for i586-unknown-linux Description: ----------- This copy of octave is from the "unstable" section of the Debian Linux distribution on ftp.debian.org. octave was working earlier, but had been getting segmentation faults while trying to reshape a large matrix. Now it won't start up at all--it gets a segmentation fault in malloc. gdb output: gigan:~> setenv OCTAVE_HOME /usr gigan:~> gdb /usr/bin/octave.bin GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i486-debian-linux), Copyright 1996 Free Software Foundation, Inc... (no debugging symbols found)... (gdb) run Starting program: /usr/bin/octave.bin (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x4012fc4a in malloc () (gdb) where #0 0x4012fc4a in malloc () #1 0x92 in ?? () #2 0x4013fd00 in __morecore () Cannot access memory at address 0x766173c9. (gdb) My system is using Linux kernel 2.0.23, libc 5.4.7 (from Debian distribution). 80MB RAM, 116MB swap, PPro 200. Repeat-By: --------- This is the second time in a week that octave has suddenly stopped working like this. I'm not sure what got it working again the previous time, but this time it stayed broken even after I completely removed the application and fetched and installed a new binary from ftp.debian.org. The failure is not completely consistent: sometimes it gives out a "segmentation fault--stopping" message, sometimes it just dies. Extremely strange. Everything else on my system is working perfectly. Fix: --- Configuration (please do not edit this section): ----------------------------------------------- uname output: Linux gigan 2.0.23 #65 Fri Oct 25 14:12:56 PDT 1996 i686 Fortran compiler: FFLAGS: -O2 -fomit-frame-pointer F2C: f2c F2CFLAGS: FLIBS: -lf2c C compiler: gcc CFLAGS: -DHAVE_CONFIG_H -mieee-fp -O2 -fomit-frame-pointer C++ compiler: c++ CXXFLAGS: -DHAVE_CONFIG_H -fno-implicit-templates -mieee-fp -O2 -fomit-frame-pointer LDFLAGS: -g DEFS: -DOCTAVE_SOURCE=1 -DOCTAVE_LITE=1 -DSEPCHAR=':' -DSEPCHAR_STR=: -DNPSOL_MISSING=1 -DQPSOL_MISSING=1 -DFSQP_MISSING=1 -DHAVE_STRFTIME=1 -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=4 -DIEEE_LITTLE_ENDIAN=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DF77_APPEND_UNDERSCORE=1 -DSTDC_HEADERS=1 -DHAVE_ASSERT_H=1 -DHAVE_FLOAT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_MEMORY_H=1 -DHAVE_PWD_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_VARARGS_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_UTSNAME_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_FCNTL_H=1 -DHAVE_SYS_RESOURCE_H=1 -DHAVE_DIRENT_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_TERMIOS_H=1 -DHAVE_SETVBUF=1 -DHAVE_GETCWD=1 -DHAVE_GETHOSTNAME=1 -DHAVE_BZERO=1 -DHAVE_BCOPY=1 -DHAVE_RINDEX=1 -DHAVE_VFPRINTF=1 -DHAVE_VSPRINTF=1 -DHAVE_STRCASECMP=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRERROR=1 -DHAVE_ATEXIT=1 -DHAVE_ON_EXIT=1 -DHAVE_TEMPNAM=1 -DHAVE_MEMMOVE=1 -DHAVE_PUTENV=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_GETRUSAGE=1 -DHAVE_LIBM=1 -DHAVE_FINITE=1 -DHAVE_ISNAN=1 -DHAVE_ISINF=1 -DHAVE_ACOSH=1 -DHAVE_ASINH=1 -DHAVE_ATANH=1 -DHAVE_ERF=1 -DHAVE_ERFC=1 -DHAVE_LGAMMA=1 -DSIGNGAM_DECLARED=1 -DRETSIGTYPE=void -DSYS_SIGLIST_DECLARED=1 -DHAVE_SYS_SIGLIST=1