linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@austin.ibm.com>
To: embedded list <linuxppc-embedded@lists.linuxppc.org>
Subject: source-level debugging w/ RISCWatch
Date: 30 Oct 2002 13:06:47 -0600	[thread overview]
Message-ID: <1036004807.11072.1289.camel@granite.austin.ibm.com> (raw)


--=-RaclAh4Sk1CquNeZPjnZ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Someone just asked me about this and I realized other people might find
it useful.

In your Makefile, CFLAGS_KERNEL   = -g -gdwarf
rw> load image zImage.treeboot <--- loads zImage onto target
rw> load host vmlinux <--- loads debugging info into RISCWatch

That's almost all it takes. Unfortunately RISCWatch will try to open
unqualified filenames, e.g. "rd.c". So you have to add to your srchpath
all the directories you're interested in:
rw> srchpath add /home/hollis/src/linux/arch/ppc/platforms
rw> srchpath add /home/hollis/src/linux/arch/ppc/kernel
rw> srchpath add /home/hollis/src/linux/kernel
......

I did this in my startup.cmd file by starting with a `find -type d` and
trimming from there.

Current (5.0) versions of RISCWatch claim to support dwarf2 which is now
the default debug format in gcc 3.x, but gcc 3.x added some extentions
that RW doesn't understand, so the load fails. I tried dwarf1 with gcc
3.x, but that fails to compile due to gcc bugs. The recommendation was
made to use gcc 2.95 with dwarf2, but that just caused RW to segfault.
I'm using dwarf1 with gcc 2.95 and that's working.

-Hollis

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~2002-10-30 19:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1036004807.11072.1289.camel@granite.austin.ibm.com \
    --to=hollis@austin.ibm.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).