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

2007-07-30 Thread Eric W. Biederman
Jan Kratochvil <[EMAIL PROTECTED]> writes: > On Mon, 30 Jul 2007 10:03:03 +0200, Vivek Goyal wrote: >> On Sat, Jul 28, 2007 at 04:43:43AM +0300, Maxim Levitsky wrote: > ... >> > gdb 'thinks' that all kernel symbols are below 0x8000 , while they are > at >> > 0xC000 >> > >> > Turning

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

2007-07-30 Thread Maxim Levitsky
On Monday 30 July 2007 11:41, Jan Kratochvil wrote: > On Mon, 30 Jul 2007 10:03:03 +0200, Vivek Goyal wrote: > > On Sat, Jul 28, 2007 at 04:43:43AM +0300, Maxim Levitsky wrote: > > ... > > > > gdb 'thinks' that all kernel symbols are below 0x8000 , while they > > > are at 0xC000 > > > > >

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

2007-07-30 Thread Jan Kratochvil
On Mon, 30 Jul 2007 10:03:03 +0200, Vivek Goyal wrote: > On Sat, Jul 28, 2007 at 04:43:43AM +0300, Maxim Levitsky wrote: ... > > gdb 'thinks' that all kernel symbols are below 0x8000 , while they are > > at > > 0xC000 > > > > Turning CONFIG_RELOCATABLE off fixes that, so I assume that

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

2007-07-30 Thread Vivek Goyal
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 0x8000 , while they are at > 0xC000 > > Turning CONFIG_RELOCATABLE off fixes that, so

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

2007-07-30 Thread Vivek Goyal
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 0x8000 , while they are at 0xC000 Turning CONFIG_RELOCATABLE off fixes that, so I

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

2007-07-30 Thread Jan Kratochvil
On Mon, 30 Jul 2007 10:03:03 +0200, Vivek Goyal wrote: On Sat, Jul 28, 2007 at 04:43:43AM +0300, Maxim Levitsky wrote: ... gdb 'thinks' that all kernel symbols are below 0x8000 , while they are at 0xC000 Turning CONFIG_RELOCATABLE off fixes that, so I assume that is the

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

2007-07-30 Thread Maxim Levitsky
On Monday 30 July 2007 11:41, Jan Kratochvil wrote: On Mon, 30 Jul 2007 10:03:03 +0200, Vivek Goyal wrote: On Sat, Jul 28, 2007 at 04:43:43AM +0300, Maxim Levitsky wrote: ... gdb 'thinks' that all kernel symbols are below 0x8000 , while they are at 0xC000 Turning

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

2007-07-30 Thread Eric W. Biederman
Jan Kratochvil [EMAIL PROTECTED] writes: On Mon, 30 Jul 2007 10:03:03 +0200, Vivek Goyal wrote: On Sat, Jul 28, 2007 at 04:43:43AM +0300, Maxim Levitsky wrote: ... gdb 'thinks' that all kernel symbols are below 0x8000 , while they are at 0xC000 Turning CONFIG_RELOCATABLE off

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

2007-07-27 Thread Eric W. Biederman
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 0x8000 , while they are at > 0xC000 > > Turning CONFIG_RELOCATABLE off fixes that, so I assume that is the

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

2007-07-27 Thread Eric W. Biederman
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 0x8000 , while they are at 0xC000 Turning CONFIG_RELOCATABLE off fixes that, so I assume that is the reason for