Re: [Xen-devel] State of gdbsx in xen-4.0-testing.hg and debugger documentation.

[Mukesh Rathor <mukesh.rathor@xxxxxxxxxx>]

On Tue, 13 Jul 2010 22:29:48 -0700
Bruce Edge <bruce.edge@xxxxxxxxx> wrote:
> The docs for using gdbsx state:
> 
>    - Additionally, to debug loadable kernel modules, please do
> following: (gdb) p init_mm.pgd[3]
>       $1 = {pgd = 0x1b874f027}
>       (gdb) monitor pgd3 0x1b874f027  (Make sure value is in HEX)
>       pgd3val set to: 0x1b874f027
> 
> When I try to use this to access a module, I get:
> 
> (gdb) p init_mm.pgd[3]
> $10 = {pgd = 0}
> (gdb)
> 
> I assume that the value of pgd should not be 0 as the makes the next
> command it the docs meaningless.
> 
> Is it possible that the field [3] offset has changed?
> What field are we after with this command?
> 

Bruce,

This for 32bit domU kernel only. I guess the README is not updated in
all trees.. I'll submit patch to do this.

Thanks,
Mukesh


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel