Maxim Levitsky <[email protected]> writes:
> Hello,
>
> Today I noticed that gdb gets confused when I try to load a vmlinux image.
> gdb 'thinks' that all kernel symbols are below 0x80000000 , while they are at
> 0xC000....
>
> Turning CONFIG_RELOCATABLE off fixes that, so I assume that is the reason for
> that.
>
> I am using 2.6.23-rc1, although I don't think that older versions are better.
>
> Best regards,
> Maxim Levitsky
Weird.
Vivek could this be related to the problem of problematic core dumps we
were seeing earlier?
Eric
> PS:
> This is what gdb says:
>
> (gdb) disassemble sys_open
> Dump of assembler code for function sys_open:
> 0x8026fa60 <sys_open+0>: Cannot access memory at address 0x8026fa60
>
> While real address of sys_open is:
>
> [root@MAIN linux-2.6]# nm ./.obj/vmlinux | grep sys_open
> .........
> c016ea60 T sys_open
>
> Strange, but gdb recordnizes the above address directly:
>
> (gdb) disassemble 0xc016ea60
> Dump of assembler code for function sys_open:
> 0xc016ea60 <sys_open+0>: sub $0x4,%esp
> 0xc016ea63 <sys_open+3>: mov 0x10(%esp),%eax
> ...............
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
