> Oct 28 06:00:13 sunset /netbsd: Data modified on freelist: word 3 of object 0xf0d0e4c0 size 56 previous type file (0xdeadbef0 != 0xdeadbeef)

> [...], and the value of the data is almost always '0xdeadbef0' or
> rarely '0xdeadbef1'.

> This suggests to me that whatever's doing the tromping also always
> just sets that last byte to either F0 or very rarely sometimes F1,
> but those values don't mean anything significant to me.

Much more likely, it seems to me, is that it's doing one, or rarely
two, increment operations.

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B