From: Keith Seitz <keiths@redhat.com>
To: j.burton@tiscali.it
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Insight Debugger Help
Date: Wed, 03 Aug 2005 20:29:00 -0000 [thread overview]
Message-ID: <1123100963.4363.8.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <42D7AA47000328BF@mail-5.mail.tiscali.sys>
On Wed, 2005-08-03 at 09:11 +0200, j.burton@tiscali.it wrote:
> Hello everybody,
> I need some help configuring insight debugger (gdb 6.0)...
> I'm using arm-elf-insight....
> I can't debug files using simulator as target device
Zowie! 6.0 is very, very old. I would very much recommend trying a newer
version (or CVS HEAD/snapshot). My memory is failing on this subject,
but I seem to recall quite a few arm-elf problems with gdb around that
time (but I could be mistaken).
> It gives me sometime a Virtual Memory Low error and others times it only
> say: can't find executable and it exits from the program window....
Hmm. Doesn't sound good. Insight (the gui) seldom crashes/exits
abnormally (or abruptly). In most cases gdb (the "backend") does this.
So let's start with the output of "insight --version". Other thing to
try is running with "insight -nw" (or "insight --i=console") and seeing
if you can manually attach to the simulator and run it. If you do this,
could you please cut and paste the entire session into an email for the
list? That would be very helpful.
Note also that many simulators require you to recompile the code for the
simulator, linking against a simulator-specific library. (In other
words, the same executable often -- not always -- does not run on both
hardware and the simulator.)
Keith
prev parent reply other threads:[~2005-08-03 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 7:11 j.burton
2005-08-03 20:29 ` Keith Seitz [this message]
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=1123100963.4363.8.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=j.burton@tiscali.it \
/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).