linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Pedro Parrilla <pparrilla@prodys.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Problems with remote debugging on MBX860
Date: Wed, 19 Sep 2001 18:04:24 +0200	[thread overview]
Message-ID: <3BA8C207.79FFF7CD@prodys.net> (raw)


 Hello!

    I am debugging  a remote target (Hard Hat Linux on a MBX860) from my

host (Red Hat Linux 7.0 on x86 PC) with ppc_8xx_gdb(cross-dev). I got to
connect both with
'target extended-remote' directive in the host, and with gdbserver in
the target, gdb can do STEP,RUN...and the like, but I can't see the
variables values. If I try to print any local variable GDB response is
'incomplete type'. I've compiled with ppc_8xx-gcc and the 'g' option and
I've  loaded the program in GDB with file 'program'...I don't Know what
more I should do...Any bad
configuration?

 Thanks.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-09-19 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-19 16:04 Pedro Parrilla [this message]
2001-09-19 16:32 ` Problems with remote debugging on MBX860 Peter Desnoyers
2001-09-20 14:28 ` Cal Erickson

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=3BA8C207.79FFF7CD@prodys.net \
    --to=pparrilla@prodys.net \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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 NNTP newsgroup(s).