In article <20040120164606.GA166@quartz.newn.cam.ac.uk>,
	Patrick Welche <prlw1@newn.cam.ac.uk> writes:
> Data modified on freelist: word 7 of object 0xc363c880 size 128 previous type bar (0xdeadbeee != 0xdeadbeef)
> Data modified on freelist: word 7 of object 0xc363c580 size 128 previous type bar (0xdeadbeee != 0xdeadbeef)
> 
> and all froze. Does that say "memory is going bad"?

Not necesarrily. The kernel could have done something like "foo->bar--" on
the overwritten memory location. But it could of cause also be a hardware
problem. A good test is to compile something big (e.g. KDE 3). If your
computer survives that without a segmentation fault from gcc the memory
is probably ok.

	Kind regards

-- 
Matthias Scheler                                  http://scheler.de/~matthias/