Re: Riscwatch Probe

Kenneth,

Try compiling with -dwarf2.  We have no problem with symbolic debug    with
riscwatch here.

You will also need to set you srchpath to inclulde the .o file that contain
the debug info

Chip

Kenneth Johansson [off-list ref]@lists.linuxppc.org on
10/21/2002 03:38:47 AM

Sent by:    owner-linuxppc-embedded@lists.linuxppc.org


To:    Aman <redacted>
cc:    Linuxppc embedded <redacted>
Subject:    Re: Riscwatch Probe




On Sat, 2002-10-19 at 20:48, Aman wrote:

Hi All

Can we use Riscwatcg Probe from IBM to debug PPCboot code.

yes and no. I could never get riscwatch software to do symbolic
debugging.

--
Kenneth Johansson
Ericsson AB                       Tel: +46 8 404 71 83
Borgafjordsgatan 9                Fax: +46 8 404 72 72
164 80 Stockholm                  kenneth.johansson@etx.ericsson.se


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

On Mon, 2002-10-21 at 07:15, Ralph Blach wrote:

Try compiling with -dwarf2.  We have no problem with symbolic debug with
riscwatch here.

You will also need to set you srchpath to inclulde the .o file that contain
the debug info

Could you be more specific? I've just built a kernel with gcc 3.2 -g
(defaults to dwarf2). What must I add to my srchpath so I can debug the
whole kernel (not a particular object file)?

Currently I have linux/ (for the vmlinux debug info?) and
linux/arch/ppc/boot/images (to load the zImage). I've loaded with 'load
image zImage.initrd.treeboot', but all the Source windows remain blank.

-Hollis

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