From: Cal Erickson <cal_erickson@mvista.com>
To: Pedro Parrilla <pparrilla@prodys.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Problems with remote debugging on MBX860
Date: Thu, 20 Sep 2001 07:28:31 -0700 [thread overview]
Message-ID: <3BA9FD0F.9293D4C3@mvista.com> (raw)
In-Reply-To: 3BA8C207.79FFF7CD@prodys.net
Pedro,
All you need to add is the -ggdb option after the -g in your build of
your application. This option provides gdb with more information
about local variables that -g cannot. Everything else should be fine.
If you were going to debug a kernel using gdb you would not be
using gdbserver.
Cal Erickson
Pedro Parrilla wrote:
> 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.
>
--
===========================================================================
Cal Erickson MontaVista Software Inc.
Linux Consultant 1237 E. Arques Ave.
Phone (408) 328-0304 Sunnyvale CA 94085
Fax (408) 328-9204 web http://www.mvista.com
===========================================================================
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-09-20 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 16:04 Problems with remote debugging on MBX860 Pedro Parrilla
2001-09-19 16:32 ` Peter Desnoyers
2001-09-20 14:28 ` Cal Erickson [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=3BA9FD0F.9293D4C3@mvista.com \
--to=cal_erickson@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pparrilla@prodys.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.