Quoting Jason Wessel <[EMAIL PROTECTED]>:
>> Um, okay..... How do I do that? My GDB Fu is weak here; how do I
>> tell gdb that the symbols in vmlinux are all offset? Or how do I
>> manipulate the vmlinux binary to offset the symbols?
>>
>
> Start gdb with no file. And do something like: add-symbol-file vmlinux
> 0xBFA00000
Um, where did you get "0xBFA0000" from? Unfortunately this didn't
work at all. I would think to get my numbers to work I'd need to
use 0xC0400000 to get sys_close to appear at 0xc047d341. And
viola, that seems to work! Or at least I got a reasonable breakpoint
from the 'target remote'
> I doubt this will fix your problem if the text and data section were
> dynamically changed or changed as a result of using something like
> kexec/kdump.
Thanks for the warning -- I'll keep that in mind. I have no idea if
the kernel build uses kexec/kdump.
>>> are not going to be able to "easily" debug kernel modules of course
>>> without patching gdb to have the kernel module support.
>
> You can elect to make manual mappings, but is automatically taken care
> of if you port the changes to gdb which are in the source forge kgdb
> repository.
I'll take a look... It would be nice if these patches got fed upstream.
> Jason.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
