Well it makes sense really. All it means is that the program is acessing memory that belongs to someone else. Usually it means something silly like trying to run functions on a null pointer or an array out of bounds, but if the OS is hosed and isn't reporting memory bounds correctly, a lot of things could seg fault.
I feel bad for that sysadmin though, I can see a bunch of retarded CS101 students going "But I heard the computer is broken if I get a seg fault!"
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.