Re: [FORGE] struct package segmentation fault

[Doug Stewart]

On Fri, Jan 24, 2014 at 7:55 PM, Juan Pablo Carbajal <address@hidden> wrote:

Backtrace attached
The crash happens always in my system.

This time I did not use -forge cause I hit the CURL issue now, so I
downloaded the last tar from OF.

Olaf, if you can spend some minutes explaining me how you read this
backtrace thingy I will really appreciate it. I promise beers or
equivalent beverage if we ever meet (still in Jena?).

I see that he didn't answer yet so maybe this will get you started.

Item #0 is the last thing that happened.

start looking at Item #22

#0  0x00007fffe5b0f5b7 in octave_value::octave_value(char const*, char) ()
   from /usr/lib/x86_64-linux-gnu/liboctinterp.so.1
#1  0x00007fffe580b723 in base_properties::factory_defaults() ()
   from /usr/lib/x86_64-linux-gnu/liboctinterp.so.1
#2  0x00007fffe580cdd1 in figure::properties::factory_defaults() ()
   from /usr/lib/x86_64-linux-gnu/liboctinterp.so.1
#3  0x00007fffe5820965 in root_figure::init_factory_properties() ()
   from /usr/lib/x86_64-linux-gnu/liboctinterp.so.1
#4  0x00007fffe572cbef in ?? ()
   from /usr/lib/x86_64-linux-gnu/liboctinterp.so.1
#5  0x00007ffff7de9856 in call_init (address@hidden, address@hidden, 
    address@hidden, address@hidden) at dl-init.c:84
#6  0x00007ffff7de9910 in call_init (env=<optimized out>, 
    argv=<optimized out>, argc=<optimized out>, l=0x770990) at dl-init.c:55
#7  _dl_init (address@hidden, argc=1, argv=0x7fffffffdc28, 
    env=0xb4e450) at dl-init.c:133
#8  0x00007ffff7dedfdf in dl_open_worker (address@hidden)
    at dl-open.c:577
#9  0x00007ffff7de96e6 in _dl_catch_error (
    address@hidden, 
    address@hidden, 
    address@hidden, 
    address@hidden <dl_open_worker>, 
    address@hidden) at dl-error.c:177
#10 0x00007ffff7ded809 in _dl_open (
    file=0xb60b48 "/home/juanpi/.octave/struct-1.0.10/x86_64-pc-linux-gnu-api-v48+/cell2fields.oct", mode=-2147483646, caller_dlopen=<optimized out>, nsid=-2, 
    argc=1, argv=0x7fffffffdc28, env=0xb4e450) at dl-open.c:667
#11 0x00007ffff08a3026 in dlopen_doit (address@hidden) at dlopen.c:66
#12 0x00007ffff7de96e6 in _dl_catch_error (objname=0x7ae340, 
    errstring=0x7ae348, mallocedp=0x7ae338, 
    operate=0x7ffff08a2fc0 <dlopen_doit>, args=0x7fffffff6b20)
    at dl-error.c:177

I hope  this has been a help to you!!! keep working up the list to item #0, but the error can be  before item #0.

this is interesting   why   run this???  "_dlerror_run"
#13 0x00007ffff08a363c in _dlerror_run (
    address@hidden <dlopen_doit>, 
    address@hidden) at dlerror.c:163

and  now __dlopen
#14 0x00007ffff08a30c1 in __dlopen (file=<optimized out>, mode=<optimized out>)
    at dlopen.c:87

It now is in   octave_dlopen_shlib::octave_dlopen_shlib (this=0xdf68a0, f=...)

#15 0x00007ffff6272d32 in octave_dlopen_shlib::octave_dlopen_shlib (
    this=0xdf68a0, f=...) at ../../stable/liboctave/util/oct-shlib.cc:197
#16 0x00007ffff6272dc1 in octave_shlib::shlib_rep::new_instance (f=...)
    at ../../stable/liboctave/util/oct-shlib.cc:512
#17 0x00007ffff6272e8d in octave_shlib::shlib_rep::get_instance (f=..., 
    address@hidden) at ../../stable/liboctave/util/oct-shlib.cc:108
#18 0x00007ffff757ee8d in octave_shlib (fake=true, f=..., this=0x7fffffff6bb0)
    at ../../stable/liboctave/util/oct-shlib.h:116

and now it is using "open"
#19 open (f=..., this=0x7fffffff6ba0)
    at ../../stable/liboctave/util/oct-shlib.h:150

now I see octave_dynamic_loader::do_load_oct
#20 octave_dynamic_loader::do_load_oct (this=<optimized out>, fcn_name=..., 
    file_name=..., relative=<optimized out>)
    at ../../stable/libinterp/corefcn/dynamic-ld.cc:270

and then see octave_dynamic_loader::load_oct
#21 0x00007ffff757efd3 in octave_dynamic_loader::load_oct (fcn_name=..., 
    file_name=..., address@hidden)
    at ../../stable/libinterp/corefcn/dynamic-ld.cc:423

see the load_fcn_from_file
#22 0x00007ffff74b172d in load_fcn_from_file (file_name=..., dir_name=..., 
    dispatch_type=..., fcn_name=..., address@hidden)
    at parse-tree/oct-parse.yy:3671

 

On Fri, Jan 24, 2014 at 10:38 PM, Olaf Till <address@hidden> wrote:
> On Fri, Jan 24, 2014 at 10:16:09PM +0100, Juan Pablo Carbajal wrote:
>> On Fri, Jan 24, 2014 at 10:13 PM, Olaf Till <address@hidden> wrote:
>> > Octave and the installation under gdb and obtain a backtrace after
>> > the crash?
>>
>> Sure, who I do this?
>> just activate debugg_on_<something> or I have to call octave with gdb?
>
> From the shell:
>
> gdb /path/to/octave
>
> Then within gdb:
>
> run
>
> Then within Octave:
>
> pkg install ....
>
> Then, if it should crash as before, you are at the gdb commandline
> again and give the command 'bt'. This should produce the backtrace. To
> quit gdb, 'kill' and 'quit'.
>
> Olaf
>
> --

--

DAS