ebiederm@xxxxxxxxxxxx (Eric W. Biederman) writes:
Derek Atkins <warlord@xxxxxxx> writes:
Well, gdb agrees with System.map, so I'm sure that gdb itself is
okay. It's certainly possible that that the kgdb stub is weird,
but /proc/kallsyms doesn't match System.map, and THAT'S what's
confusing me most of all.
Ok. So we must have a relocatable kernel that figures it has been
relocated. Interesting.
What is your bootloader?
GRUB
What is your kernel version?
2.6.22.5-76_kgdb0.fc7-i686
What is your kernel config?
See the attached .config file.
The only time I would expect to see what you are seeing is if
you are debugging the kdump kernel, which doesn't sound like
the case.
Nope. I started with the Fedora 'i686' config and then patched
in the kgdb patches and configuration.
If we actually have a truly offset kernel then while things
may not be perfect this is at least expected. I don't think
I have heard of anyone handling this case very well.
:( Like I said before, it SEEMS to work okay by telling GDB
to load in at a different address.
Which was how long ago? ;)
Long enough ago that I don't remember when ;)
Heh.
Eric
-derek
------------------------------------------------------------------------
------------------------------------------------------------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
------------------------------------------------------------------------
_______________________________________________
Kgdb-bugreport mailing list
Kgdb-bugreport@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
