From: Keith Seitz <keiths@redhat.com>
To: Ilko Iliev <iliev@caretec.at>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: problem with remote target
Date: Thu, 04 Nov 2004 17:21:00 -0000 [thread overview]
Message-ID: <1099588911.2780.0.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <418A3832.5030702@caretec.at>
On Thu, 2004-11-04 at 06:09, Ilko Iliev wrote:
> (arm-gdb) lo
> gdbarch_addr_bit called
> gdbarch_addr_bit called
> Loading section .rom_vectors, size 0x40 lma 0x800000
> gdbarch_remote_translate_xfer_address called
> Sending packet:
> $X800000,40:\016\000\000ê\030ð\237å\030ð\237å\030ð\237å\030ð\237å\000\000\000\000\030ð\237å\030ð\237å@\000\200\000<\003\200\000¤\003\200\000Ü\003\200\000<\004\200\000\000\000\000\000(\005\200\000ð\004\200\000#70...Ack
> Packet received: OK
> Memory access error while loading section .rom_vectors.
> (arm-gdb)
This is a question for the gdb folks. [Gdb is the real debugger; insight
is merely a bunch of glue code and a graphical ui.]
Ask on gdb@sources.redhat.com.
Keith
next prev parent reply other threads:[~2004-11-04 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 14:10 Ilko Iliev
2004-11-04 17:21 ` Keith Seitz [this message]
2004-11-04 17:24 ` Jon Beniston
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=1099588911.2780.0.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=iliev@caretec.at \
--cc=insight@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).