[Crash-utility] [ANNOUNCE] crash version 7.2.2 is available
Alex Sidorenko
alexandre.sidorenko at hpe.com
Thu May 17 13:48:03 UTC 2018
Well, stepping in GDB line-by-line I can see that we segfault at #1594 in filesys.c
1588 if (!one_vfsmount)
(gdb)
1589 FREEBUF(mntlist);
(gdb)
1590 if (VALID_STRUCT(mount))
(gdb)
1593 FREEBUF(vfsmount_buf);
(gdb)
1594 FREEBUF(super_block_buf);
(gdb)
1595 }
(gdb)
0x0000000000000000 in ?? ()
That is, there is definitely memory corruption somewhere and 'mount' is most probably just a victim.
Alex
On 2018-05-17 09:36 AM, Alex Sidorenko wrote:
> crash> mount
> VFSMOUNT SUPERBLK TYPE DEVNAME DIRNAME
> ffff88101c916080 ffff88081c837400 rootfs rootfs /
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000000000 in ?? ()
> (gdb) bt
> Python Exception <type 'exceptions.ImportError'> No module named gdb.frames:
> #0 0x0000000000000000 in ?? ()
> #1 0x0000000000000000 in ?? ()
--
Alex Sidorenko Expert Technologist
ERT Linux HPE Pointnext
asid at hpe.com +1 514-941-8030 Mobile
2344 Boulevard Alfred Nobel, Saint-Laurent, QC, Canada
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/crash-utility/attachments/20180517/0a46d188/attachment.htm>
More information about the Crash-utility
mailing list