From: Michael Ellerman <michael@ellerman.id.au>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org, Steve Wise <swise@opengridcomputing.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: xmon debugger doc?
Date: Fri, 13 Apr 2007 13:58:29 +1000 [thread overview]
Message-ID: <1176436709.4734.19.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <20070413034850.GA12654@lixom.net>
[-- 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 --]
prev parent reply other threads:[~2007-04-13 3:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1176410647.27519.6.camel@stevo-desktop>
2007-04-13 3:48 ` xmon debugger doc? Olof Johansson
2007-04-13 3:58 ` Michael Ellerman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1176436709.4734.19.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=swise@opengridcomputing.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).