From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <015701c41c3d$7c209770$8201a8c0@cc77109e>
From: "Bruce Ellis" <brucee@chunder.com>
To: <9fans@cse.psu.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [9fans] notify woe
Date: Wed,  7 Apr 2004 11:10:38 +1000
Topicbox-Message-UUID: 53cd5de2-eacd-11e9-9e20-41e7f4b1d025

gee, don't call malloc from a notify function, this is from mk ...

acid: stk()
sleep()+0x7 /sys/src/libc/9syscall/sleep.s:5
lock(lk=0x188b8)+0x88 /sys/src/libc/port/lock.c:22
plock(p=0x17814)+0x12 /sys/src/libc/port/malloc.c:78
poolalloc(p=0x17814,n=0x1d)+0xf /sys/src/libc/port/pool.c:1096
malloc(size=0x15)+0x1c /sys/src/libc/port/malloc.c:199
wait()+0x87 /sys/src/libc/9sys/wait.c:22
waitfor(msg=0x7fffc600)+0x8 /sys/src/cmd/mk/plan9.c:144
waitup(retstatus=0x0,echildok=0x1)+0x5a /sys/src/cmd/mk/run.c:119
killchildren(msg=0x7fffc6e8)+0x59 /sys/src/cmd/mk/run.c:269
notifyf(msg=0x7fffc6e8)+0x7b /sys/src/cmd/mk/plan9.c:294
notifier+0x30 /sys/src/libc/port/atnotify.c:15

actually don't call wait, or any library function that allocates,
from a notify function.  how's my timing in interrupting a malloc?

brucee