NetBSD Problem Report #1234

From gnats  Fri Jul 14 13:42:07 1995
Received: from pgoyette.bdt.com (root@pgoyette.bdt.com [204.182.11.88]) by sun-lamp.pc.cs.cmu.edu (8.6.11/8.6.10) with ESMTP id NAA12414 for <gnats-bugs@gnats.netbsd.org>; Fri, 14 Jul 1995 13:42:03 -0400
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:         1234
>Category:       test
>Synopsis:       chat REPORT function does not work as documented
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    gnats-admin
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 17 14:12:49 +0000 1995
>Closed-Date:    Mon Jul 17 14:58:48 +0000 1995
>Last-Modified:  Thu May 05 08:35:45 +0000 2011
>Originator:     Paul Goyette
>Release:        NetBSD-current 7/14/95<NetBSD-current source date>
>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 14:58:48 1995
State-Changed-Why:

>Unformatted:

Home	PR Database Search