[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 29 Aug 2007 21:13:10 -0500
From: Jason Wessel <jason.wessel@...driver.com>
To: pete@...elane.com
CC: Andrew Morton <akpm@...ux-foundation.org>,
kgdb-bugreport@...ts.sourceforge.net, amitkale@...syssoft.com,
linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org,
Mariusz Kozlowski <m.kozlowski@...land.pl>,
Paul Mackerras <paulus@...ba.org>
Subject: Re: [Kgdb-bugreport] 2.6.23-rc3-mm1: kgdb build failure on powerpc
Pete/Piet Delaney wrote:
> We are getting a problem with VMware where kernel text is the schedler
> is getting wacked with four null bytes into the code. Thought I'd use
> the current linux-2.6-kgdb.git tree and possible the CONFIG_DEBUG_RODATA
> patch to make kernel text readonly:
>
> https://www.x86-64.org/pipermail/patches/2007-March/003666.html
>
> I thought the kernel text was RO and gdb had to disable it to
> insert a breakpoint.
>
>
If you are going to make all the kernel text RO, then you are going to
have to add some code to the kgdb write memory so as to unprotect a
given page or all the breakpoint writes are going to fail.
Alternatively you can use HW breakpoints. But, I have no idea if your
VM Ware simulated HW emulate HW breakpoint registers or not.
Jason.
-
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/
Powered by blists - more mailing lists