Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.411 (Entity 5.404)
RT-Send-CC:
X-RT-Original-Encoding: iso-8859-1
Content-Length: 1055

In doing some experimenting and syscall tracing, I'm finding that output
produced right before the child process exits may not be read properly
by expect.  For example, a failure in test 8 had this sequence of calls:

5123/1:		93.4088	write(7, "\n", 1)				= 1
5313/1:		93.4088	read(0, "\n", 1024)				= 1
5313/1:		93.4102
open("/var/krbsnap/autobuild-static/work-20030923.0842/krb5-current/src/kadmin/testing/krb5-test-root/kdb5.kadm5.lock",
O_RDWR|O_CREAT|O_EXCL, 0600) = 4
5313/1:		93.4109	write(1, " r e l e a s e d\n", 9)		= 9
5313/1:		93.4113	llseek(4, 0, SEEK_CUR)				= 0
5313/1:		93.4115	close(4)					= 0
5313/1:		93.4121	_exit(0)
...
5123/1:		93.4283	poll(0xFFBFBAD0, 1, 60000)			= 1
5123/1:			fd=7  ev=POLLRDNORM|POLLRDBAND rev=POLLERR
5123/1:		93.4288	read(7, 0x000EEC20, 4096)			Err#22 EINVAL

Here fd 7 had previously been used successfully for reading and writing
while the child process was alive.  But after the process exits, the
output that had been sent is not available.

This behavior *could* be new to (running the tests on) Solaris 9.