public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
* Debugging the kernel with BDI2000
@ 2003-01-15  0:13 Xiaogeng (Shawn) Jin
  0 siblings, 0 replies; only message in thread
From: Xiaogeng (Shawn) Jin @ 2003-01-15  0:13 UTC (permalink / raw)
  To: support, 'linuxppc-embedded@lists•linuxppc.org'


I tried to debug the kernel with BDI2000 and gdb and had some problems.

I wanted to set a breakpoint at console_init() and did the following steps.
(1) BDI>bi 0xc00020f0    # stop at start_here
(2) BDI>go
ppcboot was running and loaded the kernel image and stoped at start_here.
(3) BDI>ci
(4) ppc_8xx-gdb vmlinux    # start gdb
(gdb) target remote bdi:2001
(gdb) b console_init

The above steps were all successful. But when I wanted to step by 'n' or
continue the execution by 'cont'. I got the following error.

(gdb) cont
warning: Cannot insert breakpoint -1:
Error accessing memory address 0xc0000000: Unknown error 4294967295.

What does this mean? My BDI2000 configuration may not right? CPU is 855.

Thanks.
- shawn.


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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2003-01-15  0:13 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-01-15  0:13 Debugging the kernel with BDI2000 Xiaogeng (Shawn) Jin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox