linux-kernel - Re: [BUG] i386 relocable kernel breakes /proc/kcore debugging

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070730080303.GA6071@in.ibm.com>
Date:	Mon, 30 Jul 2007 13:33:03 +0530
From:	Vivek Goyal <vgoyal@...ibm.com>
To:	Maxim Levitsky <maximlevitsky@...il.com>
Cc:	linux-kernel@...r.kernel.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	jan.kratochvil@...hat.com
Subject: Re: [BUG] i386 relocable kernel breakes /proc/kcore debugging

On Sat, Jul 28, 2007 at 04:43:43AM +0300, Maxim Levitsky wrote:
> 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.
> 

This is a gdb issue. I had raised it in gdb mailing list some time back.

http://sourceware.org/ml/gdb/2006-08/msg00137.html

What version of gdb you are using? I know it got fixed for gdb shipped
with RHEL5. I am not sure about what upstream version of gdb it got fixed
in.

I think Jan Kratochvil had put a patch to fix the issue. I am copying him
on the mail and he should be able to tell which version of gdb to use.

Thanks
Vivek
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/