This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/165: GDB doesn't recover gracefully from remote protocol errors.
- To: gdb-gnats at sources dot redhat dot com
- Subject: gdb/165: GDB doesn't recover gracefully from remote protocol errors.
- From: ac131313 at cygnus dot com
- Date: 7 Jul 2001 03:25:30 -0000
- Reply-To: ac131313 at cygnus dot com
>Number: 165
>Category: gdb
>Synopsis: GDB doesn't recover gracefully from remote protocol errors.
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Jul 06 20:28:23 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: ac131313@cygnus.com
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
GDB doesn't recover gracefully from remote protocol errors.
GDB wasn't checking for NAKs from the remote target. Instead a NAK is
ignored and a timeout is required before GDB retries. A pre-cursor to
fixing this this is making GDB's remote protocol packet more robust.
While downloading to a remote protocol target, gdb ignores packet
errors in so far as it will continue to download with chunk N+1 even
if chunk N was not correctly sent. This causes gdb.base/remote.exp to
take a painfully long time to run. As a PS that test needs to be
fixed so that it builds on 16 bit machines.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: