[Ilugc] segmentation faults
- From: andyetitmoves@xxxxxxxxx (Ramkumar R)
- Date: Fri Jan 27 00:56:21 2006
segmentations faults have got nothing to do with your ram. MALLOC_CHECK_
is
really? i had the same problem for some 2 years... random segfaults and
crashes... worse was the fact that i was moving from windows to linux at
that time, and linux used to crash more than windows, and this even made me
lose trust on the os for some time! serendipitously happened to run the
memtest86 shipped with fedora and found memory errors. what it needed after
that was just the badram patch... (i reasoned out later that, ironically,
linux crashed more because it utilized the available RAM more :) )
dude... you *do* get a segfault when a memory error flips a bit in the
address where you have a pointer stored!
debian is generally stable (unless u use the unstable strain), and if you
get random errors in many apps, then there is a good possibility that the
bug is in the kernel (if you use a custom kernel) or the hardware.
memtest is a boot time program and doesnt depend on the OS (why talk abt the
distro then!)... all you need is a bootable iso with the program (fc2 used
to ship it in... i dunno if this is the case now.. i've stopped using fc)...
memtest cannot solve the hardware problem! memtest can isolate regions of
your memory which are erroneous though... you will have to use the "badram"
patch to the kernel to pass these faulty address ranges at boot time, so
that the kernel locks these pages early on in the boot process, and no
process or the kernel ends up using them....
it moves on...
--
WARN_(accel)("msg null; should hang here to be win compatible\n");
-- WINE source code
Other related posts:
