l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2004 Aug 27 10:28

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: Fwd: Re: [vox-tech] debian woody to sarge upgrade =dead xserver: solved
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fwd: Re: [vox-tech] debian woody to sarge upgrade =dead xserver: solved

On Thursday 26 August 2004 19:08, Jonathan Stickel wrote:
> Ken Bloom wrote:
> > On Thu, 26 Aug 2004 15:12:51 -0700
> >
> > Rick Moen <rick@linuxmafia.com> wrote:
> >>Quoting Ken Bloom (kabloom@ucdavis.edu):
> >>>I don't think that's correct. Signal 11 is better known as SIGSEGV,
> >>>and it is a segmentation fault usually caused by a programmer
> >>>dereferencing an uninitialized pointer (or a deleted pointer). It's
> >>>entirely a programmer error.
> >>
> >>Well, congratulations on encountering so little bad RAM.  ;->  Our
> >>experience differs.
> >>
> >>Quoting (selectively) a small piece of the SIG 11 FAQ:
> >>
> >>
> >>   Ok. I may have a hardware problem what is it?
> >>
> >>
> >>   If it happens to be the hardware it can be:
> >>
> >>    * Main memory.
> >>    [...]
> >
> > My main experience with segfaults, when I've cared enough to figure out
> > what was going on, has been when I've been writing C++ programs that
> > used new and delete. If you're going to debug a segfault, you need to
> > debug for a software problem first, and you need to debug for it
> > exhaustively to make sure it's not a software problem - that includes
> > sending strace/ltrace/valgrind/whatever output to the developer
> > and asking them what they think. *Then* you can conclude it's a hardware
> > problem.
> Well, if its new or suspect hardware, you can boot up memtest86(+).
I recently did have some bad memory and I did get segfaults. But I also got
illegal instructions and even unknown error. A couple of times the system 
simply stopped working and required a hardware reset. The fact that the
problem was not consistently related to what software was running, indicated
a hardware problem. Running memtest86+ confimed it.

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Sunset Systems
Who graciously hosts our website & mailing lists!