You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello!
I am using 6LBR on a small BBB-like linux box, that is a data acquisition system. I would like to follow debian releases, and am now going to walk from "jessie" through "stretch" to "bullsye" (debian 8-9-10).
With "jessie" and "stretch" before June 2019, the cetic_6lbr_router process works fine. But with newer stretch and bullsye, I have a crush with the message "corrupted size vs. prev_size". Some Googleing (for example) shows that this message is generated by libc6 during dynamic memory workout if the buffer is underflowed-overflowed, double free or whatever.
I found that the libc6 version has grown from 2.19-18 to 2.24-11 inside the stretch release somewhere in June 2019, and v2.19-18 is now strongly deprecated.
Have you ever seen such behavior?
Well, I'm not familiar with FreeRTOS debugging... I tried running cetic_6lbr_router under gdbserver and systrace, without any applicable information.
Under GDB stepping is too long..., and when I send "continue" - I got a SIGABT with "corrupted size vs prev_size" and GDB can't roll back the call stack after it.
Systrace log also does not give me applicable information.
So, could you provide me with some suggestions?
(gdb) c
Continuing.
[Detaching after fork from child process 599]
[Detaching after fork from child process 605]
[Detaching after fork from child process 628]
Program received signal SIGABRT, Aborted.
0xb6e866f6 in ?? () from target:/lib/arm-linux-gnueabihf/libc.so.6
(gdb) bt
#0 0xb6e866f6 in ?? () from target:/lib/arm-linux-gnueabihf/libc.so.6
#1 0xb6e943cc in raise () from target:/lib/arm-linux-gnueabihf/libc.so.6
#2 0xb6e950ba in abort () from target:/lib/arm-linux-gnueabihf/libc.so.6
#3 0xb6ebbcda in ?? () from target:/lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
P.S. Yes, I've rebuild cetic_6lbr_router in new system enviroment, both stretch and bullsye... no changes.
The text was updated successfully, but these errors were encountered:
Hello!
I am using 6LBR on a small BBB-like linux box, that is a data acquisition system. I would like to follow debian releases, and am now going to walk from "jessie" through "stretch" to "bullsye" (debian 8-9-10).
With "jessie" and "stretch" before June 2019, the cetic_6lbr_router process works fine. But with newer stretch and bullsye, I have a crush with the message "corrupted size vs. prev_size". Some Googleing (for example) shows that this message is generated by libc6 during dynamic memory workout if the buffer is underflowed-overflowed, double free or whatever.
I found that the libc6 version has grown from 2.19-18 to 2.24-11 inside the stretch release somewhere in June 2019, and v2.19-18 is now strongly deprecated.
Have you ever seen such behavior?
Well, I'm not familiar with FreeRTOS debugging... I tried running cetic_6lbr_router under gdbserver and systrace, without any applicable information.
Under GDB stepping is too long..., and when I send "continue" - I got a SIGABT with "corrupted size vs prev_size" and GDB can't roll back the call stack after it.
Systrace log also does not give me applicable information.
So, could you provide me with some suggestions?
That's tail of strace log:
That's end of GDB session:
P.S. Yes, I've rebuild cetic_6lbr_router in new system enviroment, both stretch and bullsye... no changes.
The text was updated successfully, but these errors were encountered: