Dave Reed wrote:
> Let's not start any misconceptions. Sig 11's are usually due to
> faulty hardware (RAM), but segmentation faults are usually a bug in
> the software.
Dave, a SIG 11 _is_ SIGSEGV, a segmentation violation. I think the
distinction that is generally made is that if you are getting segfaults
in the _compiler_, which is currently a very stable and trusted piece of
software, then you may have bad ram (it still could be a real bug in the
compiler, but probably only if the sig11 is random). If you are getting
segv in another application, then you probably will look at that
application to find the problem. Not may applications are as stable as
your compiler (and that's a damn shame).
> > On Sun, 25 Jun 2000, Mike W wrote:
> > > I know someone explained this before but I lost the email. I'm getting a
> > > segmentation fault when I try to run linuxconf. Where do I find which
> > > configuration file is the problem?
I usually use strace to find the problem. Make sure that you have the
strace package installed, and then run linuxconf like:
strace linuxconf 2> /tmp/strace.linuxconf
The file /tmp/strace.linuxconf should now have a complete stack trace
from linuxconf, up to the point that it died. Now, try:
grep open /tmp/strace.linuxconf | tail
The last file open()d is usually the cause of the problem.
Let me know whether that helps or not.
MSG
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
