[Pkg-octave-devel] octave3.0 crashes on startup
Thomas Weber
thomas.weber.mail at gmail.com
Thu Jan 10 08:29:51 UTC 2008
Hi,
we need some help. octave3.0 crashes on startup on ARM (#458852).
I attach a backtrace, provided by Soeren Sonnenburg (it's also in the
BTS).
=====================================================================
OK, I've recompiled octave w/ -O2 -g and it dies on loading
dispatch.oct. This could be enough info for upstream to fix it.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x40022490 (LWP 11491)]
0x40db4890 in octave_shlib::make_shlib ()
from /usr/lib/octave-3.0.0/liboctave.so
(gdb) bt
#0 0x40db4890 in octave_shlib::make_shlib ()
from /usr/lib/octave-3.0.0/liboctave.so
#1 0x401f7584 in octave_dynamic_loader::do_load_oct (
this=<value optimized out>, fcn_name=@0xbedd5664, file_name=@0xbedd5660,
relative=false) at ../liboctave/oct-shlib.h:52
#2 0x401f7f54 in octave_dynamic_loader::load_oct (fcn_name=@0xbedd5664,
file_name=@0xbedd5660, relative=false) at dynamic-ld.cc:508
#3 0x40469150 in load_fcn_from_file (nm_arg=@0xbedd5714, exec_script=true)
at parse.y:3440
#4 0x40469878 in load_fcn_from_file (sym_rec=0xf71658, exec_script=true)
at parse.y:3480
#5 0x40519554 in lookup (sym_rec=0xf71658, exec_script=true)
at variables.cc:1111
#6 0x408021e4 in tree_identifier::do_lookup (this=0xf6fe38,
script_file_executed=@0xbedd59e7, exec_script=true) at pt-id.cc:110
#7 0x408038e0 in tree_identifier::rvalue (this=0xf6fe38, nargout=1)
at pt-id.cc:161
#8 0x408024c4 in tree_identifier::rvalue (this=0xbedd5450) at pt-id.cc:204
#9 0x4080b72c in tree_index_expression::rvalue (this=0xf71958, nargout=0)
at pt-idx.cc:279
#10 0x4083db18 in tree_statement::eval (this=0xf6f080, silent=false,
nargout=0, in_function_body=false) at pt-stmt.cc:133
#11 0x4083e50c in tree_statement_list::eval (this=0xf66428, silent=false,
---Type <return> to continue, or q <return> to quit---
nargout=0) at pt-stmt.cc:190
#12 0x404672e8 in parse_and_execute (f=0xf60620) at parse.y:2864
#13 0x40467c68 in parse_fcn_file (ff=@0xbedd633c, exec_script=true,
force_script=true) at parse.y:3336
#14 0x40468308 in source_file (file_name=@0xbedd6460, context=@0xbedd6458)
at parse.y:3613
#15 0x402eeac4 in execute_pkg_add_or_del (dir=@0xf40098,
script_file=@0xbedd650c) at load-path.cc:1232
#16 0x402eedd8 in execute_pkg_add (dir=@0xf40098) at load-path.cc:1240
#17 0x402f3960 in load_path::do_set (this=0xf38c80, p=@0xbedd66ac, warn=false)
at load-path.cc:454
#18 0x402f3c1c in load_path::do_initialize (this=0xf38c80,
set_initial_path=true) at load-path.cc:382
#19 0x404427b8 in octave_main (argc=1, argv=0xbedd6b14, embedded=0)
at load-path.h:51
#20 0x424de040 in __libc_start_main () from /lib/libc.so.6
Backtrace stopped: frame did not save the PC
(gdb) up 2
#2 0x401f7f54 in octave_dynamic_loader::load_oct (fcn_name=@0xbedd5664,
file_name=@0xbedd5660, relative=false) at dynamic-ld.cc:508
508 ? instance->do_load_oct (fcn_name, file_name, relative) : false;
Current language: auto; currently c++
(gdb) p fcn_name
$1 = (const string &) @0xbedd5664: {static npos = 4294967295,
_M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0xf662ec "dispatch"}}
(gdb) p file_name
$2 = (const string &) @0xbedd5660: {static npos = 4294967295,
_M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>},
_M_p = 0xf7247c "/usr/lib/octave/3.0.0/oct/arm-unknown-linux-gnu/dispatch.oct"}}
(gdb)
=====================================================================
The main question is: is it a problem in Octave or something else?
Thanks
Thomas
More information about the Pkg-octave-devel
mailing list