Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <Michael.Snyder@palmsource.com>
To: "Bizhan Gholikhamseh (bgholikh)" <bgholikh@cisco.com>
Cc: gdb@sourceware.org
Subject: Re: Error running remote gdb
Date: Wed, 30 Aug 2006 23:08:00 -0000	[thread overview]
Message-ID: <1156979328.31253.4.camel@localhost.localdomain> (raw)
In-Reply-To: <F795765B112E7344AF36AA911279641502D19B30@xmb-sjc-212.amer.cisco.com>

On Wed, 2006-08-30 at 14:54 -0700, Bizhan Gholikhamseh (bgholikh) wrote:
>  Hi
> On our custome based powerpc we are running Linux 2.6.11.
> I am trying to run a sample debug session with gdbserver.
>  
> On target board I typed:
> gdbserver <host ip address>:portno <test program>
>  
> Then on host system I  typed:
> gdb <test program>
> gdb> target extended-remote <target IP addr>:portno
> gdb> b main
> gdb> cont
>  
> Then I got the following error on my host;
> Ignoring packet erro, continuing...
> Ignoring packet erro, continuing...
> Reply contains invalid hex digit 116

Most likely, your gdbserver and your gdb have not agreed on
a particular PPC architecture and register set.  So gdbserver
will send a message to gdb containing the register values, but
gdb will think that the message is the wrong size.

You can narrow this down by telling gdb:

	set debug remote on

before issuing the "target remote" command.

If this is the problem, it will be resolved by determining the
best-match PPC architecture and setting gdb to expect that 
architecture before connecting, by using the "set architecture"
command.

Michael



  parent reply	other threads:[~2006-08-30 23:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30 21:54 Bizhan Gholikhamseh (bgholikh)
2006-08-30 21:56 ` Daniel Jacobowitz
2006-08-30 23:08 ` Michael Snyder [this message]
2006-08-30 22:37 Bizhan Gholikhamseh (bgholikh)
2006-08-30 23:11 ` Michael Snyder
2006-08-31  0:39 Bizhan Gholikhamseh (bgholikh)
2006-08-31 22:47 ` Michael Snyder
2006-08-31 23:28   ` Daniel Jacobowitz
2006-09-01  3:13     ` Michael Snyder
2006-09-01  4:08       ` Daniel Jacobowitz
2006-09-01  0:33 Bizhan Gholikhamseh (bgholikh)
2006-09-01  0:35 ` Daniel Jacobowitz
2006-09-01  3:31 ` Michael Snyder
2006-09-01  4:09   ` Daniel Jacobowitz
2006-09-02  0:05     ` Michael Snyder
2006-09-02  1:04       ` Daniel Jacobowitz
2006-09-06 11:47 Bizhan Gholikhamseh (bgholikh)
2006-09-07 22:48 ` Michael Snyder
     [not found] <F795765B112E7344AF36AA911279641502D19B97@xmb-sjc-212.amer.cisco.com>
2006-09-08  1:27 ` Michael Snyder
2006-09-08  2:12   ` Daniel Jacobowitz
2006-09-08  1:30 FW: " Bizhan Gholikhamseh (bgholikh)
2006-09-08  1:53 ` Michael Snyder
2006-09-08  2:01 Bizhan Gholikhamseh (bgholikh)

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=1156979328.31253.4.camel@localhost.localdomain \
    --to=michael.snyder@palmsource.com \
    --cc=bgholikh@cisco.com \
    --cc=gdb@sourceware.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