[9fans] Okay, who's been playing with the cheese wiz?

[Dan Cross <cross@math.psu.edu>]

I've run into a couple of weird things recently.  First, I noticed that
acme was commiting suicide after I tried to delete everything in a window
using, ``Edit 1,$d'' and then tried to edit normally.  A stack trace for
that follows:

acid: lstk()
At pc:0x00039bc1:abort /sys/src/libc/9sys/abort.c:6
abort() /sys/src/libc/9sys/abort.c:6
	called from error+0x33 /sys/src/cmd/acme/util.c:55
error(s=0x000400b1) /sys/src/cmd/acme/util.c:51
	called from bufread+0xca /sys/src/cmd/acme/buff.c:287
bufread(b=0x000941c0,q0=0x00000254,n=0x00000001,s=0x00087b96) /sys/src/cmd/acme/buff.c:280
	called from textreadc+0x46 /sys/src/cmd/acme/text.c:486
	m=0x0003f878
textreadc(q=0x00000254,t=0x00093ed0) /sys/src/cmd/acme/text.c:478
	called from textbacknl+0x62 /sys/src/cmd/acme/text.c:1153
	r=0xc37f0000
textbacknl(n=0x00000012,p=0x00000255,t=0x00093ed0) /sys/src/cmd/acme/text.c:1139
	called from textshow+0xc3 /sys/src/cmd/acme/text.c:809
	i=0x00000011
	j=0x0000007f
textshow(q0=0x00000256,t=0x00093ed0,doselect=0x00000001,q1=0x00000256) /sys/src/cmd/acme/text.c:789
	called from texttype+0xf9 /sys/src/cmd/acme/text.c:553
texttype(t=0x00093ed0,r=0x0000000a) /sys/src/cmd/acme/text.c:521
	called from wintype+0x18 /sys/src/cmd/acme/wind.c:274
	nnb=0x00093de0
	q1=0x000003ad
	q0=0x0001dc38
	i=0x00093df0
	nb=0x0001dbe0
	u=0x0002db50
	n=0x00000002
wintype(t=0x00093ed0,r=0x0000000a,w=0x00093de0) /sys/src/cmd/acme/wind.c:270
	called from rowtype+0xce /sys/src/cmd/acme/rows.c:274
	i=0x00000000
rowtype(row=0x00048720,p=0x000003ad,r=0x0000000a) /sys/src/cmd/acme/rows.c:257
	called from keyboardthread+0xb2 /sys/src/cmd/acme/acme.c:386
	t=0x00093ed0
	w=0x00093de0
keyboardthread() /sys/src/cmd/acme/acme.c:351
	called from launcher386+0x10 /sys/src/libthread/386.c:10
	r=0xfee1000a
	timer=0x00098008
	t=0x00093df4
launcher386(arg=0x00000000,f=0x00001f99) /sys/src/libthread/386.c:7
	called from 0xfefefefe ?file?:0
acid:

I was away last week, so thought perhaps this was a known bug that had
been fixed elsewhere.  When I got back, I noticed a bunch of acme updates,
so I rebuilt the system to try and get everything to work again, but
now execnet dies with:

fid/qid mismatch in walk1 functionexecnet 223: suicide: sys: trap: fault read addr=0x0 pc=0x00008154

A stack trace follows:

acid: lstk()
At pc:0x00008154:abort /sys/src/libc/9sys/abort.c:6
abort() /sys/src/libc/9sys/abort.c:6
	called from oldwalk1+0x5e /sys/src/lib9p/srv.c:288
oldwalk1(arg=0x0001813c,fid=0x00036690,name=0x00028cd2) /sys/src/lib9p/srv.c:273
	called from walkandclone+0xb6 /sys/src/lib9p/srv.c:151
	qid=0x00000001
walkandclone(clone=0x0000f71d,r=0x00036250,arg=0x0001813c,walk1=0x0000f68d) /sys/src/lib9p/srv.c:131
	called from swalk+0x131 /sys/src/lib9p/srv.c:334
	i=0x00000000
swalk(srv=0x0001813c,r=0x00036250) /sys/src/lib9p/srv.c:303
	called from srv+0x182 /sys/src/lib9p/srv.c:711
srv(srv=0x0001813c) /sys/src/lib9p/srv.c:692
	called from _post2+0x47 /sys/src/lib9p/_post.c:39
_post2(v=0x0001813c) /sys/src/lib9p/_post.c:31
	called from launcher386+0x10 /sys/src/libthread/386.c:10
	s=0x0001813c
launcher386(arg=0x0001813c,f=0x000125dd) /sys/src/libthread/386.c:7
	called from 0xfefefefe ?file?:0
acid:

I thought that was pretty bizarre.  Anyway, acme continues to crash,
and now I get this, as well:

acme: bufread: internal error: '/lib/font/bit/lucidasans/lsr.14.0' does not exist

I don't recall having seen that previously.  Also, `win' is behaving
pretty bizarrely; if I type a command in a ``win'' window, I get:
``rc: note: '', a Peter face, the rc dies, and the window hangs.

This is using the latest code from sources; I pulled last night and
rebuilt everything: userland and the kernel, this morning.

I've had a really really terrible two and a half weeks and so havn't
looked into any of this myself.  Anyone else have any ideas?

	- Dan C.