> >We've also been experiencing crashes which can be induced at will with pine.
> >(This is an old copy compiled before upgrading to 1.0)
> >[...]
> 
> Just curious ... has anyone tried running ktrace on the process to figure out
> exactly _which_ system call is causing the crash?
> 
> --Ken

If its any use, here is a kdump of the second pine startup that caused the panic.
the last few lines are as follows:

   337 pine     RET   read 1023/0x3ff
   337 pine     CALL  utimes(0xf7bfbb0c,0xf7bfba78)
   337 pine     NAMI  "/var/mail/root"
   337 pine     RET   utimes 0
   337 pine     CALL  close(0x3)
   337 pine     RET   close 0
   337 pine     CALL  break(0xfeffc)
   337 pine     RET   break 0
   337 pine     CALL  stat(0xe9380,0xf7bfc258)
   337 pine     NAMI  "/var/mail/root"
   337 pine     RET   stat 0
   337 pine     CALL  break(0x107ffc)
   337 pine     RET   break 0
   337 pine     CALL  open(0xe93a0,0x202,0x1b6)
   337 pine     NAMI  "/tmp/.4.8c01"
   337 pine     RET   open 3
   337 pine     CALL  flock(0x3,0x6)
   337 pine     RET   flock 0
   337 pine     CALL  chmod(0xe93a0,0x1b6)
   337 pine     NAMI  "/tmp/.4.8c01"
   337 pine     RET   chmod 0
   337 pine     CALL  getpid
   337 pine     RET   getpid 337/0x151
   337 pine     CALL  write(0x3,0xf7bfc33c,0x4)
(END)

If you want the while trace file, let me know and I can mail it out.

bry
---
 Bryan Collins
 Coombs Computing Unit
 Australian National University
 Canberra, Australia, 0200
 Tel: (06) 249 5586
 Fax: (06) 257 1893
 Email: Bryan.Collins@anu.edu.au