On Fri, 16 Apr 1999, Oded Arbel wrote:
>ScryMUD
Does it happen to be an alpha version ? Did you read all the docs ? Does
it say it will work on your machine ?
>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
You got a kernel oops probably. It must be in the system logs, too, so you
can peel it out of there and email it.
>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.
Yes.
>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.
Does your MUD daemon perhaps introduce a kernel device or module ? You can
only have such drastic crashing by messing with kernel code directly.
Did you try to switch to another console and issue commands from there ?
If a simple compile fails, you should get a simple sigsegv, maybe a core.
NO crash. However, if some pages in your swap partition got corrupted
because the disk was overloaded during compile... you might see what you
saw. Find them oopses in the logs and try to make sense of them. Just out
of curiosity.
Peter
