From: Keith Seitz <keiths@redhat.com>
To: "Heik H. Hellmich" <hellmich@mikro.ee.tu-berlin.de>
Cc: insight@sources.redhat.com
Subject: Re: step through code
Date: Wed, 25 Sep 2002 08:34:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0209250818340.1512-100000@valrhona.uglyboxes.com> (raw)
In-Reply-To: <3D9196F3.50E0A9F0@mikro.ee.tu-berlin.de>
On Wed, 25 Sep 2002, Heik H. Hellmich wrote:
> I am using Insight GNU gdb 5.1 (--host=sparc-sun-solaris2.6
> --target=powerpc-eabi) and have the problem that I cannot step through
> the generated elf-code because the step/next/finish/continue buttons are
> always greyed out for target=sim. I am able to load the elf-file and can
> see the c-file and the corresponding asm-file in Insight's source
> window.
This usually happens when gdb fails to set an inferior pid (which is/was
gdb's goofy way of knowing whether an inferior exists), but it could be
anohter error getting in the way. If you enter "tk ManagedWin::open
DebugWin" in the console window, it will open a debug window. Clear it
before you click run and send the results after you have clicked run and
it fails to do anything.
Can you also send the results of typing "tk gdb_target_has_execution" and
"tk set ::gdb_running". This will tell us if inferior_pid is set.
I've tried this on CVS head, and it works on my ADS executable on the
simulator. You could simply upgrade to 5.2 or 5.3 or just use CVS head
sources.
Keith
next prev parent reply other threads:[~2002-09-25 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 3:58 Heik H. Hellmich
2002-09-25 8:34 ` Keith Seitz [this message]
[not found] <3D9323DB.C90B70D3@mikro.ee.tu-berlin.de>
2002-09-26 8:49 ` Keith Seitz
[not found] <3D948874.99C32AFE@mikro.ee.tu-berlin.de>
2002-09-27 9:56 ` Keith Seitz
[not found] <3D9491C7.84727946@mikro.ee.tu-berlin.de>
2002-09-27 10:18 ` Keith Seitz
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=Pine.LNX.4.44.0209250818340.1512-100000@valrhona.uglyboxes.com \
--to=keiths@redhat.com \
--cc=hellmich@mikro.ee.tu-berlin.de \
--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).