xmon debugger doc?

xmon debugger doc?

[Steve Wise]

Can someone please point me at ppc64 xmon debugger usage /
documentation? I've had little luck finding info on-line.

Thanks in advance,

Steve.

Re: xmon debugger doc?

[Olof Johansson]

On Thu, Apr 12, 2007 at 03:44:07PM -0500, Steve Wise wrote:
> Can someone please point me at ppc64 xmon debugger usage /
> documentation? I've had little luck finding info on-line.

The help output from it is pretty much all there is.

You might have better luck asking on linuxppc-dev@ozlabs.org though
(adding as Cc).

There's also an old writeup at
http://mbligh.org/linuxdocs/Kernel/DebuggingPPC64 for the very basics
of digging through a crash. Some of it is likely out of date by now.


-Olof

Re: xmon debugger doc?

[Olof Johansson]

On Thu, Apr 12, 2007 at 03:44:07PM -0500, Steve Wise wrote:
> Can someone please point me at ppc64 xmon debugger usage /
> documentation? I've had little luck finding info on-line.

The help output from it is pretty much all there is.

You might have better luck asking on linuxppc-dev@ozlabs.org though
(adding as Cc).

There's also an old writeup at
http://mbligh.org/linuxdocs/Kernel/DebuggingPPC64 for the very basics
of digging through a crash. Some of it is likely out of date by now.


-Olof

Re: xmon debugger doc?

[Michael Ellerman]

[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]

On Thu, 2007-04-12 at 22:48 -0500, Olof Johansson wrote:
> On Thu, Apr 12, 2007 at 03:44:07PM -0500, Steve Wise wrote:
> > Can someone please point me at ppc64 xmon debugger usage /
> > documentation? I've had little luck finding info on-line.
> 
> The help output from it is pretty much all there is.
> 
> You might have better luck asking on linuxppc-dev@ozlabs.org though
> (adding as Cc).
> 
> There's also an old writeup at
> http://mbligh.org/linuxdocs/Kernel/DebuggingPPC64 for the very basics
> of digging through a crash. Some of it is likely out of date by now.

A good trick which the help output doesn't mention is that % and $ are
special in input, so you can do:

0:mon> di %pc

disassemble instructions at address pointed to by register PC

Other regs are eg: %lr, %r1, %r12.
And it works with di, d and other commands.

Also:

0:mon> di $.xmon_register_spus

disassemble instructions at address of symbol .xmon_register_spus.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: xmon debugger doc?

[Michael Ellerman]

[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]

On Thu, 2007-04-12 at 22:48 -0500, Olof Johansson wrote:
> On Thu, Apr 12, 2007 at 03:44:07PM -0500, Steve Wise wrote:
> > Can someone please point me at ppc64 xmon debugger usage /
> > documentation? I've had little luck finding info on-line.
> 
> The help output from it is pretty much all there is.
> 
> You might have better luck asking on linuxppc-dev@ozlabs.org though
> (adding as Cc).
> 
> There's also an old writeup at
> http://mbligh.org/linuxdocs/Kernel/DebuggingPPC64 for the very basics
> of digging through a crash. Some of it is likely out of date by now.

A good trick which the help output doesn't mention is that % and $ are
special in input, so you can do:

0:mon> di %pc

disassemble instructions at address pointed to by register PC

Other regs are eg: %lr, %r1, %r12.
And it works with di, d and other commands.

Also:

0:mon> di $.xmon_register_spus

disassemble instructions at address of symbol .xmon_register_spus.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]