https://bugzilla.kernel.org/show_bug.cgi?id=27492
--- Comment #10 from Dave Chinner <david@xxxxxxxxxxxxx> 2011-02-04 00:13:10 ---
(In reply to comment #9)
> (In reply to comment #8)
> > The trace in comment #6 is _not a crash_. It's a filesystem shutdown
> > because a
> OK - I would not use this word anymore ;-)
> > transaction failed. That's what is supposed to happen, and it tells you
> > this:
> >
> > Filesystem "dm-7": Corruption of in-memory data detected. Shutting down
> > filesystem: dm-7
> > Please umount the filesystem, and rectify the problem(s)
> >
> > As to gdb failing to work, try just running "gdb vmlinux" and running
> > 'l *(xfs_da_do_buf+0x4c8)' at the command prompt once it has started.....
> >
>
> root@ittest01:~ (master $ u=) # gdb /usr/src/linux/vmlinux
> GNU gdb (Gentoo 7.2 p1) 7.2
> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i686-pc-linux-gnu".
> For bug reporting instructions, please see:
> <http://bugs.gentoo.org/>...
> Reading symbols from /usr/src/linux-2.6.37/vmlinux...(no debugging symbols
> found)...done.
> (gdb) l *(xfs_da_do_buf+0x4c8)
> No symbol table is loaded. Use the "file" command.
You need to build your kernel with debugging symbols:
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_EXTRA_PASS=y
Just rebuilding it with these additional options set should not change the code
at all, but should allow gdb to work.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
|