From: "Setty, Vinay J (Vinay)** CTR **" <vinaysetty@lucent.com>
To: gdb@sources.redhat.com
Subject: 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 08:44:00 -0000 [thread overview]
Message-ID: <6117ACCB57BFD4118C0C00508BB1B920051FC604@ii3004exch001u.in.lucent.com> (raw)
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...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Remote packet too long:
01000000dc341200080100a000000000ba552206ba552206dc4000000000000000000000ffff
0000000000000000ffff0000000000000000ffff0000000000000000ffff0000000000000000
0000000000000000000000000000ba552206ba552206dc440800b4632a06e82c0b0602000000
1000000008000000080000000800000008000000080000000000000000000000ffff00000000
000000000000ffff0000000000000000ffff0000000000000000ffff00000000000000000000
0000000000000000000
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Remote packet too long:
01000000dc341200080100a000000000ba55200008000000080000000000000000000000ffff
0000000000000000ffff0000000000000000ffff0000000000000000ffff0000000000000000
000000000000080100a000000000ba552206ba552206dc440800b4632a06e82c0b0602000000
1000000008000000080000000800000008000000080000000000000000000000f000000ffff0
000000000000000ffff0000000000000000ffff0000000000000000ffff00000000000000000
0000000000000000000
Ignoring packet error, continuing...
Remote packet too long:
01000000dc341200080100a000000000ba50000ba552206ba552206dc440800b4632a06e82c0
b06020000001000000008000000080000000800000008000000080000000000000000000000f
fff00000000000000000000000ffff0000000000000000ffff0000000000000000ffff000000
0000000000000000000000000000000000000000000000000000000000000004632a06e82c0b
06020000001000000008000000080000000800000008000000080000000000000000000000ff
ff0000000000000000f
Ignoring packet error, continuing...
Remote packet too long:
01000000dc341200080100a000000000ba00000ba552206ba552206dc440800b4632a06e82c0
b06020000001000000008000000080000000800000008000000080000000000000000000000f
fff00000000000000000000000ffff0000000000000000ffff0000000000000000ffff000000
000000000000000000000000000000000000000000000000000000000000004632a0--
-Type <return> to continue, or q <return> to quit---
If any of u have any solution please tell me, it would be of great help.
Thanks in advance
Regards,
Vinay Setty,
Project Intern,
Lucent Technologies,
Extn: 2045
Direct: 51191045
next reply other threads:[~2005-05-16 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 8:44 Setty, Vinay J (Vinay)** CTR ** [this message]
2005-05-16 10:22 ` Steven Johnson
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=6117ACCB57BFD4118C0C00508BB1B920051FC604@ii3004exch001u.in.lucent.com \
--to=vinaysetty@lucent.com \
--cc=gdb@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