-----BEGIN PGP SIGNED MESSAGE-----

On Mon, 6 Nov 2000, Todd Vierling wrote:

> I'll look at it, but no guarantees at the moment.
> 
> This has happened before, and I cannot currently place what it was that
> caused it.  It happened somewhere around Pine 4.02 or something like that.

If it jogs any memories, here's an excerpt from a kdump under NetBSD
1.4/i386:

  7675 pine     CALL  open(0xefbf9c54,0x4,0x402f8060)
  7675 pine     NAMI  "/usr/home/alaric/mail/"
  7675 pine     RET   open 5
  7675 pine     CALL  __fstat13(0x5,0xefbf9bbc)
  7675 pine     RET   __fstat13 0
  7675 pine     CALL  fcntl(0x5,0x2,0x1)
  7675 pine     RET   fcntl 0
[... getdents and lseek and close and stuff like that ...]
  7675 pine     CALL  setitimer(0,0xefbfb484,0xefbfb474)
  7675 pine     RET   setitimer 0
  7675 pine     CALL  __sigprocmask14(0x1,0xefbfbf64,0xefbfbf54)
  7675 pine     RET   __sigprocmask14 0
  7675 pine     CALL  __sigprocmask14(0x3,0xefbfbf70,0xefbfbf60)
  7675 pine     RET   __sigprocmask14 0
  7675 pine     CALL  __sigprocmask14(0x1,0xefbfbf60,0xefbfbf50)
  7675 pine     RET   __sigprocmask14 0
  7675 pine     CALL  __sigprocmask14(0x3,0xefbfbf6c,0xefbfbf5c)
  7675 pine     RET   __sigprocmask14 0
  7675 pine     CALL  gettimeofday(0xefbfbfa4,0)
  7675 pine     RET   gettimeofday 0
  7675 pine     CALL  __sigprocmask14(0x1,0xefbfbf54,0xefbfbf44)
  7675 pine     RET   __sigprocmask14 0
  7675 pine     CALL  __sigprocmask14(0x3,0xefbfbf60,0xefbfbf50)
  7675 pine     RET   __sigprocmask14 0
  7675 pine     CALL  getpid
  7675 pine     RET   getpid 7675/0x1dfb
  7675 pine     CALL  __sigprocmask14(0x1,0xefbfbefc,0xefbfbeec)
  7675 pine     RET   __sigprocmask14 0
  7675 pine     CALL  __sigprocmask14(0x3,0xefbfbf08,0xefbfbef8)
  7675 pine     RET   __sigprocmask14 0
  7675 pine     CALL  __sigprocmask14(0x1,0xefbfbf4c,0xefbfbf3c)
  7675 pine     RET   __sigprocmask14 0
  7675 pine     CALL  __sigprocmask14(0x3,0xefbfbf58,0xefbfbf48)
  7675 pine     RET   __sigprocmask14 0
  7675 pine     PSIG  SIGSEGV caught handler=0x166264 mask=() code=0x6

Calls to sigprocmask14 with first param 0x1 block certain signals, param
0x3 sets the signal mask. ktrace doesn't show me the signal sets, but it
looks as if the SIGSEGV was blocked when it happened, but popped out as
soon as it was unblocked... this theory would seem to place it around the
mailbox access stuff, the gettimeofday, or the getpid; I doubt it's
lingered since before then.

This occurs at the point of hitting "c" for compose, not when *sending*
the mail, for me.

ABS

- -- 
                       Alaric B. Snell BEng ACGI
 http://www.alaric-snell.com/  http://RF.Cx/  http://www.warhead.org.uk/
   Any sufficiently advanced technology can be emulated in software  

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
Charset: noconv

iQEVAwUBOgdbhOMilTCx2ct3AQHn9wf+NOQfIV9Oi+fe0cvxM92Hv9cxn1xsFb7O
8JHFiDCVzV/kvYXJhPpJPGsSd4VXZu3ALyyu7WGaqzbA9sAOZWyRyu2cVUKX5/7u
76xLblScpKgbAAW7rSqDSzBXXmPswt8RV9mFg1llFw/D7eCRiOXOW4hibLVBAmO7
CVvYeUvNgeKDup14A/zppCUVptsR52orMEHi9bKuDYWsPkYzlhyPRbZLfC0adG08
azeVr59lq0A2LzEusycRjzH+Y0JqLyUFvdOkccFuHjvp5bkcJ8Pb8xZ3xhAl65Lj
KAKoZje2hjmgtV8c8NMjb1cHGSUW+/nmxzdU9L58CZ63XVD/5eGeBQ==
=8vLS
-----END PGP SIGNATURE-----