OK, I think I get it - a segfault means that either my prog is buggy or my
hardware is buggy.
and I have a problem with accepting either of those explanations - here some
more info:
I tried to 'make all' a program I downloaded, called ScryMUD (it's a MUD
daemon).
after compiling several things, it reported an error ( I don't remember
which, and I don't have the dump on this computer) and stopped compiling . I
then tried to view the make file, using pico (Y pico ? I don't know - it
seemed like a good idea at the time) at which point the system refused to
run pico and responded with segfault. I don't know exactly, but I recon that
pico is written well enough so as not to cause segmentation faults.
the next thing that happend is that I got some sort of kernel panic message,
involving some thing about the CPU (I don't remember exactly the phrasing,
except that it was full of register names and stuff like that - I think I
kind of panicked my self ;-> ) and I couldn't do anything else, not even a
proper reboot (pressing CTRL-ALT-DEL got me another endless flow of panic
messages and nothing else) so I had to go for the big red button.
about the hardware - it's an old P75, but I had the memory upgraded to lots
of MBs, and it's quite new (the memory - considering it's an EDO) and I
didn't had any problems with the system at all (hardware wise) except for
some small HDD glitches which is understandable considering the age of both
drives (one is 420M). the only reboots that the system got were during power
failurs (no UPS yet, but I'm working on it) and some that I did myself
before I knew how to kill and restart system services :-).
I would realy like some suggestions at to what do you think caused the
segmentation fault.
Oded
--
----------------------------------------------------
Technology is a way of organizing the universe so that man doesn't have to
experience it.
-- Max Frisch
