Subject: Re: squid now reveals a new kernel problem.
To: John Kohl <email@example.com>
From: Bill Studenmund <firstname.lastname@example.org>
Date: 10/28/1999 09:46:31
On Thu, 28 Oct 1999, John Kohl wrote:
> >>>>> "Greg" == Greg A Woods <email@example.com> writes:
> Greg> Oct 28 06:00:13 sunset /netbsd: Data modified on freelist: word 3 of object 0xf0d0e4c0 size 56 previous type file (0xdeadbef0 != 0xdeadbeef)
> Greg> This suggests to me that whatever's doing the tromping also always just
> Greg> sets that last byte to either F0 or very rarely sometimes F1, but those
> Greg> values don't mean anything significant to me.
> Looks to me like 0xdeadbeef ++ (maybe twice). Somebody's using a
> counter that has been freed?
Or beef++ or ef++. Is the machine big or little endian?