Declan Moriarty wrote:
[...]
%
% The result is in this limited mode, that if you try to grab something off the
% wrong page, you get a segmentation fault. But linux requires a 386+ because
% it never wants to use this stupid way of going on in the first place (GOOD
% WORK, LINUS!). When you see "Segmentation Fault", that cpu is in real mode,
% the application is has gone off the rails and switched the cpu to real mode
% which I don't think linux ever uses. So there's either a dud compiler, dud
% support files, dud disk, dud rpm, or dud something. Time for the M$ solution
% (delete & reinstall). Lastly, don't take all of this as gospel; I'm an
% electronic hardware type, with no authority on software issues.
Segmentation faults occur when there is an illegal memory access of
any type. In software, it most often occurs when when referencing a
undefined pointer or accessing unallocated memory (outside of an
array, for example). In Linux, applications cannot drop the CPU
into real mode -- the kernel controls this. Moreover, the kernel
*does* use real mode, but only at boot time, and it jumpts to
protected mode fairly early.
Kurt
--
Ben, why didn't you tell me?
-- Luke Skywalker
_______________________________________________
Linux-users mailing list
Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
