From: Keith Seitz <keiths@redhat.com>
To: Mike Smith <msmith@trinityconvergence.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Problems with remote debugging
Date: Tue, 16 Sep 2003 13:44:00 -0000 [thread overview]
Message-ID: <1063720002.1589.3.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <004601c37c32$9dae9820$4801a8c0@Arrows>
On Tue, 2003-09-16 at 02:12, Mike Smith wrote:
> I'm having problems trying to debug a remote xScale system with Insight
> 5.3. I've built Insight for a xscale-arm-elf target. If I use the
> version of gdb generated everything works fine and I can debug away.
> However, when I run Insight things are not so happy. I set up the
> target settings for Remote/TCP connection, to Attach to Target, not to
> Download Program, and to 'Continue from Last Stop' as Run Method. When
> I run, the connection gets set up to the gdbserver but then I get
> 'Program Received signal SIGSEGV, Segmentation Fault'. On the bash
> terminal on the host I get:
> /bin/bash: 'my_prog': cannot execute binary file
> /bin/bash: 'my_prog': Success
What is "my_prog"? Is this your debug executable? If so, it appears that
gdb is attempting to run it natively. What host are you on?
Can you show me a gdb session (command line) of what you're doing (the
part that works)? Any messages in the debug window? (Open console, type
"tk ManagedWin::open DebugWin" to open.)
Are you using a stub -- err, debug agent -- or gdbserver. I wasn't aware
that gdbserver worked on anything other than native targets. Even if it
did, it would almost certainly require a download.
Keith
next prev parent reply other threads:[~2003-09-16 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 9:10 Mike Smith
2003-09-16 13:44 ` Keith Seitz [this message]
2003-09-16 15:06 ` Mike Smith
2003-09-16 20:05 Rod Boyce
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=1063720002.1589.3.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=msmith@trinityconvergence.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).