NetBSD Problem Report #1237
Received: (from root@localhost) by pgoyette.bdt.com (8.6.12/8.6.11) id XAA02632; Fri, 14 Jul 1995 23:38:30 -0700
Message-Id: <199507150638.XAA02632@pgoyette.bdt.com>
Date: Fri, 14 Jul 1995 23:38:30 -0700
From: paul@pgoyette.bdt.com
Reply-To: paul@pgoyette.bdt.com
To: gnats-bugs@gnats.netbsd.org
Subject: chat REPORT function does not work as documented
X-Send-Pr-Version: 3.2
>Number: 1237
>Category: bin
>Synopsis: chat REPORT function does not work as documented
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: bin-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Jul 18 01:05:04 +0000 1995
>Closed-Date: Tue Jul 18 01:12:11 +0000 1995
>Last-Modified: Wed Aug 07 23:36:30 +0000 2002
>Originator: Paul Goyette
>Release: NetBSD-current 7/14/95
>Organization:
--------------------------------------------------------------------
| Paul Goyette | Key available via finger or key server |
| Paul@pgoyette.bdt.com | Fingerprint: 0E 40 D2 FC 2A 13 74 A0 |
| | E4 69 D5 BE 65 E4 56 C6 |
--------------------------------------------------------------------
>Environment:
Mac IIci, NetBSD-current, chat
System: NetBSD pgoyette.bdt.com 1.0A NetBSD 1.0A (PGOYETTE) #30: Fri Jul 14 19:38:53 PDT 1995 paul@pgoyette.bdt.com:/usr/src/sys/arch/mac68k/compile/PGOYETTE mac68k
>Description:
REPORT feature does not work quite as documented. In
particular, if the current "expected" string is found
in the middle of or concurrent with a REPORT string,
the REPORT string is never reported.
Additionally, if the REPORT string is found, that string
and all subsequent characters, up to the next control
character OR the end of the current "expected" string
are written to the report file.
This appears to be a result of the code resetting the
contents of the receive buffer as soon as the expected
string is found; this doesn't leave any of the earlier
characters around for matching with the REPORT string(s).
>How-To-Repeat:
Create a chat script with a REPORT string identical to
an expected string, for example REPORT CONNECT.
>Fix:
Unknown
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed
State-Changed-By: jtc
State-Changed-When: Mon Jul 17 15:12:11 1995
State-Changed-Why:
>Unformatted:
CGD 8/19: KILLED LOSSAGE-INDUCING BINARY CHARACTERS.
an expected string, for example REPORT CONNECT.
the REPORT string is never reported.
Additionally, if the REPORT string is found, that string
and all subsequent characters, up to the next control
character OR the end of the current "expected" string
are written to the report file.
This appears to be a result of the code resetting the
contents of the receive buffer as soon as the expected
string is found; this doesn't leave any of the earlier
characters around for matching with the REPORT string(s).
System: NetBSD pgoyette.bdt.com 1.0A NetBSD 1.0A (PGOYETTE) #30: Fri Jul 14 19:38:53 PDT 1995 paul@pgoyette.bdt.com:/usr/src/sys/arch/mac68k/compile/PGOYETTE mac68k
particular, if the current "expected" string is found
in the middle of or concurrent with a REPORT string,
the REPORT string is never reported.
Additionally, if the REPORT string is found, that string
and all subsequent characters, up to the next control
character OR the end of the current "expected" string
are written to the report file.
This appears to be a result of the code resetting the
contents of the receive buffer as soon as the expected
string is found; this doesn't leave any of the earlier
characters around for matching with the REPORT string(s).
an expected string, for example REPORT CONNECT.
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.