Weird signal issues using yocto's warrior busybox (aarch64) when memory is cached

Sergio Paracuellos sergio.paracuellos at gmail.com
Thu Jan 30 18:23:27 UTC 2020


Hi Michael,

On Thu, Jan 30, 2020 at 5:38 PM Michael Conrad <mconrad at intellitree.com> wrote:
>
> 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 am able to reproduce the issue using different SOMs with its own RAM
chip on it, and its own mmc storage device where the system is
installed so I
am pretty sure the hardware is not the problem here.

> I just had a USB thumb drive corrupt a file with no warning, so it was
> fresh on my mind.
>
> -Mike

Thanks for the advice and your time.

Best regards,
    Sergio Paracuellos

>
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox


More information about the busybox mailing list