On 1/30/2020 12:53 AM, Sergio Paracuellos wrote:
warning: core file may not match specified executable file. [New LWP 23217]warning: Could not load shared library symbols for 3 libraries, e.g. /lib/libm.so.6. Use the "info sharedlibrary" command to see the complete listing. Do you need "set solib-search-path" or "set sysroot"? Core was generated by `sleep 1'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0xfffffcd7fffffc60 in ?? () (gdb) bt #0 0xfffffcd7fffffc60 in ?? () #1 0x000000555668af74 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) (gdb) Look at the PC (0xfffffcd7fffffc60) at this point.. It has not sense at all. For me it looks like a stack corruption.
First things first, do you trust the hardware? If the system swapped out some pages and then read them back in and the controller or storage device gave back bad data, this could cause all sorts of crashes. Maybe run a memtest, too, unless you can reproduce the issue on multiple different machines.
I just had a USB thumb drive corrupt a file with no warning, so it was fresh on my mind.
-Mike _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
