From: "Q-ha Park" <qha@infoeq.com>
To: <bradbosch@attbi.com>, "'Mark A. Greer'" <mgreer@mvista.com>,
<wd@denx.de>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: using bdi2000 to debug ppcboot on mpc7455
Date: Wed, 1 Oct 2003 15:57:45 +0900 [thread overview]
Message-ID: <000501c387e9$52901590$2a21a8c0@qha> (raw)
In-Reply-To: <16242.64239.133401.668446@waldo.lisle.iphase.com>
Soft breakpoints just don't work for me. I have two BDI tools, and they
behave the same. Not only that, "next", "step", and other commands just
don't work properly.
Here's what I get:
(gdb) add-symbol-file ppcboot 0x1ffc0000
add symbol table from file "ppcboot" at
.text_addr = 0x1ffc0000
(y or n) y
Reading symbols from ppcboot...done.
(gdb) b board_init_r
Breakpoint 1 at 0x1ffc2cb0: file board.c, line 570.
(gdb) d
Delete all breakpoints? (y or n) y
(gdb) mon bi 0x1ffc2cb0 v
Breakpoint identification is 0
///// I have to use "mon bi" to make the program stop properly.
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
Cannot remove breakpoints because program is no longer writable.
It might be running in another process.
Further execution is probably impossible.
board_init_r (bd=0x1ff3fffa, dest_addr=536084376) at board.c:570
570 {
------------------------
(gdb) b flash_init
Breakpoint 2 at 0x1ffd4100: file flash.c, line 330.
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
Cannot remove breakpoints because program is no longer writable.
It might be running in another process.
Further execution is probably impossible.
board_init_r (bd=0x1ff3fffa, dest_addr=536084376) at board.c:570
570 {
/////// It stopped at board_init_r again..... not flash_init
(gdb) d
Delete all breakpoints? (y or n) y
(gdb) b flash_init
Breakpoint 3 at 0x1ffd4100: file flash.c, line 330.
(gdb) c
Continuing.
warning: Cannot insert breakpoint -1:
Error accessing memory address 0xfff00100: Unknown error 4294967295.
(gdb)
And now I get this. Did anyone go thru something like this?
Q-ha Park
-----Original Message-----
From: bradbosch@attbi.com [mailto:bradbosch@attbi.com]
Sent: Thursday, September 25, 2003 11:26 PM
To: Mark A. Greer; Q-ha Park; linuxppc-embedded@lists.linuxppc.org
Subject: Re: using bdi2000 to debug ppcboot on mpc7455
<snip>
//// OK. Now we are in RAM and we can use soft breakpoints from here
//// on out.
(gdb) b board_init_r
Breakpoint 6 at 0xffc14a0: file board.c, line 589.
(gdb) cont
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
after_reloc (gd=0xff96f9c, dest_addr=268140544) at db64360.c:416
416 board_init_r(gd, dest_addr);
(gdb) list
=======================
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-01 6:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 0:56 using bdi2000 to debug ppcboot on mpc7455 Q-ha Park
2003-09-25 2:33 ` Mark A. Greer
2003-09-25 14:25 ` bradbosch
2003-09-25 18:27 ` Mark A. Greer
2003-09-26 5:52 ` Q-ha Park
2003-09-30 21:35 ` Wolfgang Denk
2003-09-30 21:32 ` Wolfgang Denk
2003-10-01 6:57 ` Q-ha Park [this message]
2003-10-01 10:29 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2003-09-30 22:39 Rod Boyce
2003-09-30 23:38 ` Wolfgang Denk
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='000501c387e9$52901590$2a21a8c0@qha' \
--to=qha@infoeq.com \
--cc=bradbosch@attbi.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mgreer@mvista.com \
--cc=wd@denx.de \
/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).