On Fri, 2001-12-28 at 18:01, Michel Lanners wrote: > > What kernel are you running? > > Either 2.2.19 (Debian install kernel) or 2.2.18-presomething (LinuxPPC 2000 > Q4 install kernel).
I assume those should be solid, or there would be more reports of this kind. > > Spurious segfaults can only really be caused by libc, the kernel or > > hardware, or am I missing something? > > I don't know if you can call these 'spurious', since they _always_ happen on > kernel compile, Always in the same place? > but (so far) on nothing else. I think memory has been exercised enough during > install and > during first tests (running Mozilla and konqueror at the same time under > Gnome ;-). It would > really be a very bad coincidence to always hit that bad memory block on > kernel compile. Those things happen, you know. ;) > Which leaves libc: but why doesn't anything else that uses libc segfault then? Yes, I haven't experienced libc related crashes in a looong time. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast
