public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Xiaogeng (Shawn) Jin" <xjin@redswitch•com>
To: support@abatron•ch,
	"'linuxppc-embedded@lists•linuxppc.org'"
	<linuxppc-embedded@lists•linuxppc.org>
Subject: Debugging the kernel with BDI2000
Date: Tue, 14 Jan 2003 16:13:41 -0800	[thread overview]
Message-ID: <3E24A7B5.7000500@redswitch.com> (raw)


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/

                 reply	other threads:[~2003-01-15  0:13 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=3E24A7B5.7000500@redswitch.com \
    --to=xjin@redswitch$(echo .)com \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    --cc=support@abatron$(echo .)ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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