Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Steven Johnson <sjohnson@sakuraindustries.com>
To: "Setty, Vinay J (Vinay)** CTR **" <vinaysetty@lucent.com>
Cc: gdb@sources.redhat.com
Subject: Re: Ignoring packet error, continuing... with --host=sparc-sun-solari s2.5.1 --target=i386-coff using GNU gdb 4.17-intelp2-990419
Date: Mon, 16 May 2005 10:22:00 -0000	[thread overview]
Message-ID: <4289AA86.9090809@sakuraindustries.com> (raw)
In-Reply-To: <6117ACCB57BFD4118C0C00508BB1B920051FC604@ii3004exch001u.in.lucent.com>

Hi Vinay,

The response you are going to get is "Your version of GDB is 6 years 
old, we suggest you upgrade to a newer version and try that".

Ignoring packet error, continuing...

means your target is sending data that your version of GDB doesnt like.  
This is possible because your target is newer that the version of GDB 
you are using, and the Remote Protocol probably has changed in the last 
6 years.  At least to the extent that there may be new features or 
replies your old version of GDB doesnt support. It could also be for any 
number of other reasons, all of which, including this one, would be 
speculation.

The only way you are going to track this is turn on Remote Serial 
protocol debuging (I dont know how to do this in V4.17, check your docs) 
and then look at the messages your version of GDB is sending, and what 
it is receiving in reply, and what it expects to receive. (Again check 
your docs, the remote serial protocol should be documented in there).  
You also may want to check the code, sometimes things like case 
sensitivity of hex numbers, and the like arent well documented.  So your 
target sends a hex number in uppercase, but for that response GDB only 
likes lower case (that sort of thing).  So if it looks right with your 
understanding of the doc, check the code for more enlightenment.  If its 
this sort of thing, you will have to either modify your target, or GDB 
so they can understand one another.

I know this isnt a very helpful reply, but is there any reason why you 
have to use a 6 year old version of GDB?  If you can use a newer 
version, you might want to try that, and save frustration.  You may be 
left with the same problem, but at least you will know it isnt because 
of your vintage GDB.

Steven Johnson


Setty, Vinay J (Vinay)** CTR ** wrote:

>Hi all,
>I am using GNU gdb 4.17-intelp2-990419 with --host=sparc-sun-solaris2.5.1
>--target=i386-coff configuration options and my target intel pentium II
>achitecture is connected throught an ethernet serial port. and I am running
>gdb client in solaris workstation. The problem is whenever I try to give any
>command in gdb clinet I get the following error. some times I am able to set
>the break point but if I give continue it doesn't stop at the break point.
>
>The error is :
>Ignoring packet error, continuing...
>  
>


      reply	other threads:[~2005-05-16 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16  8:44 Setty, Vinay J (Vinay)** CTR **
2005-05-16 10:22 ` Steven Johnson [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=4289AA86.9090809@sakuraindustries.com \
    --to=sjohnson@sakuraindustries.com \
    --cc=gdb@sources.redhat.com \
    --cc=vinaysetty@lucent.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