"Tony Chung" <[EMAIL PROTECTED]> writes:

> Amit,
>
> I examined the gdb source code and inserted some fprintf to debug.
> I found it is related to symbols add_modsects and modules.
>>From System.map, they are:
>
> c078da20 d modules
> c0446d94 T add_modsects
>
> When print inside gdbmod-2.4:
>
> (gdb) print add_modsects
> return val is 0x9c773c8 for modified_name add_modsects
> $1 = {int (struct module *, Elf32_Ehdr *, Elf32_Shdr *, 
>     const char *)} 0x80846d94 <add_modsects>
>
> It was off by 0x9600000.
> When I used the stocked FC6 gdb, the address matched the one in
> System.map. So the gdb is incorrectly patched?  

Could this be related to https://bugzilla.redhat.com/show_bug.cgi?id=309751
where the kernel doesn't run at the offset it was compiled for?

-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: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport

Reply via email to