From: "Frank Ch. Eigler" <fche@redhat.com>
To: Robert Cragie <rcc@jennic.com>
Cc: sid@sources.redhat.com
Subject: Re: Trying to run on pid7t board
Date: Wed, 21 Aug 2002 09:35:00 -0000 [thread overview]
Message-ID: <20020821123523.B7180@redhat.com> (raw)
In-Reply-To: <NDBBLOIOMLKELOJBAPAGEEHNCOAA.rcc@jennic.com>; from rcc@jennic.com on Wed, Aug 21, 2002 at 05:24:50PM +0100
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
Hi -
On Wed, Aug 21, 2002 at 05:24:50PM +0100, Robert Cragie wrote:
> [...]
> I then connect to it using gdb (insight 5.0), and connect successfully to
> the target. I then download the test, and inspect memory at 0x8000, no
> problem, it's there. However, when I start to run, it hits the breakpoint I
> have set, but I notice all the code has vanished at 0x8000, and it's
> executing 0x00000000 each time. Any idea what's going on?
Yes, that is odd. Can you tell me why you think it's executing 0x0?
You could show gdb's side of the conversation, either a console script,
or maybe even include packet traces as per `(gdb) set remote debug 3'.
> [...]
> I am suspicious of the 'flush_i_cache' line - could this be flushing 0
> into the program space?:
> [...]
I don't think so. The only cache in the pid7t configuration is a little
instruction-decoding cache inside the CPU model, and flushing it just means
throwing it away. The instruction memory should not be affected at all.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-08-21 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 9:24 Robert Cragie
2002-08-21 9:35 ` Frank Ch. Eigler [this message]
2002-08-21 11:15 ` Robert Cragie
2002-08-21 11:31 ` Frank Ch. Eigler
2002-08-22 4:48 ` Robert Cragie
2002-08-22 6:22 ` Frank Ch. Eigler
2002-08-22 7:11 ` Ben Elliston
2002-08-22 10:09 ` Robert Cragie
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=20020821123523.B7180@redhat.com \
--to=fche@redhat.com \
--cc=rcc@jennic.com \
--cc=sid@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).