help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Octave-2.1.50 startup segfault on ARM (SA1110)


From: Simon Pickering
Subject: Octave-2.1.50 startup segfault on ARM (SA1110)
Date: Tue, 23 Dec 2003 11:04:33 -0600

Hello All,

I thought it was about time to try cross-compiling 2.1.50 (I did 2.0.17
when it came out and it works fine on my Zaurus sl5500). I get a SEGSIGV
as soon as I start the binary. I did a search of the mailing lists but
didn't come up with anything in particular other than making sure that
your libc headers were correct for the lib you're using. They are. I
wonder whether anyone on the list could give me some suggestions?

I used a GCC 2.95.3 ARM cross-compiler on an i686 Mandrake 9.1 box. I
didn't sent it with this email as it's quite long but I have the
config.log file handy if it contains something which may be of help.

I am running (or rather trying to run) Octave on a Sharp Zaurus Sl5500
(SA1110 processor, 64MB RAM) with an OZ3.3.5 ROM (for those who care
;-). This is what I get on my Zaurus (it runs as root by default BTW):

# ./octave-2.1.50
panic: Segmentation fault -- stopping myself...
attempting to save variables to `octave-core'...
save to `octave-core' complete
SIGSEGV
#

Dmesg shows nothing of interest (I don't know whether it ought to).

Strace shows the following (just the end part):

brk(0x314b000)                          = 0x314b000
brk(0x314c000)                          = 0x314c000
brk(0x314d000)                          = 0x314d000
brk(0x314e000)                          = 0x314e000
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
write(2, "panic: ", 7panic: )                  = 7
write(2, "Segmentation fault", 18Segmentation fault)      = 18
write(2, " -- stopping myself...\n", 23 -- stopping myself...
) = 23
write(2, "attempting to save variables to "..., 49attempting to save
variables to `octave-core'...
) = 49
open("octave-core", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0664) = 3
gettimeofday({1071877632, 977179}, NULL) = 0 write(2, "save to
`octave-core\' complete\n", 31save to `octave-core' complete
) = 31
close(3)                                = 0
rt_sigaction(SIGSEGV, {SIG_DFL}, {0x21a335c, [], 0x4000000}, 8) = 0
getpid()                                = 1551
kill(1551, SIGSEGV)                     = 0
sigreturn()                             = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++


Gdb shows the following:

# gdb --se=octave-2.1.50
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are welcome to change it and/or 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. This
GDB was configured as "arm-linux-gnu"...
(gdb) run
Starting program: /mnt/cf/octave-2.1.50

Program received signal SIGSEGV, Segmentation fault.
0x023bf1c4 in default_save_header_format ()
   at
/skiff/local/lib/gcc-lib/arm-linux/2.95.2/../../../../include/g++-3/std/
bastring.h:109
109
/skiff/local/lib/gcc-lib/arm-linux/2.95.2/../../../../include/g++-3/std/
bastring.h: No such file or directory.
       in
/skiff/local/lib/gcc-lib/arm-linux/2.95.2/../../../../include/g++-3/std/
bastring.h
Current language:  auto; currently c++
(gdb)

bastring.h does exist, and there's no #include etc. on the line to which
it refers. Any ideas?

Thanks,


Simon

--------------------------------------------
Simon Pickering MEng
Dept. of Mechanical Engineering
University of Bath
Bath, BA2 7AY, UK

Tel: +44 (0)1225 383314
Fax: +44 (0)1225 386928
--------------------------------------------
 



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------



reply via email to

[Prev in Thread] Current Thread [Next in Thread]