[Olsr-dev] olsrd2 / coredump

Bastian Bittorf (spam-protected)
Wed Nov 23 11:42:38 CET 2016

dear hard working coders!

first of all: greeting from the biggest
olsrd2-testnet in the world 8-) with 70 real nodes.

and: what is the best place for such reports?
for now i have this on different platforms
with recent LEDE and v0.13.0-4-gfc4e019

(spam-protected):~/ledebot/source 8( scripts/remote-gdb
Using target mipsel_24kc (musl-1.1.15)
GNU gdb (GDB) 7.12
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
and "show warranty" for details.
This GDB was configured as "--host=x86_64-linux-gnu
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Find the GDB manual and other documentation resources online at:
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from
debugging symbols found)...done.
[New LWP 2277]
warning: Can't read pathname for load map: Unknown error -1.
Core was generated by `/usr/sbin/olsrd2 --set global.fork=true --load
Program terminated with signal SIGSEGV, Segmentation fault.
#0  free (p=0x77db92b0) at src/malloc/malloc.c:450
450             if (IS_MMAPPED(self)) {
(gdb) bt full
#0  free (p=0x77db92b0) at src/malloc/malloc.c:450
        self = 0x77db92a8
        next = <optimized out>
        final_size = <optimized out>
        new_size = <optimized out>
        size = <optimized out>
        reclaim = 0
#1  0x0042a881 in netaddr_acl_remove ()
No symbol table info available.
#2  0x0040b255 in oonf_packet_free_managed_config ()
No symbol table info available.
warning: GDB can't find the start of the function at 0x40c358.

    GDB is unable to find the start of the function at 0x40c358
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
    This problem is most likely caused by an invalid program counter or
stack pointer.
    However, if you think GDB should simply search farther back
from 0x40c358 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
#3  0x0040c359 in ?? ()
No symbol table info available.

More information about the Olsr-dev mailing list