Re: SEGFAULTS???

Albert Cahalan (albert@ccs.neu.edu)
Wed, 17 Apr 1996 16:02:52 -0400 (EDT)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Andrew E. Mileski: "Re: 16 MB -> 32 MB, a memory problem resolved!"
Previous message: Zen: "I can't compile Kernel 1.3.83+"

>> Why does moving a 486 register to another register fail as
>> as "Segmentation fault"?
>> Can anyone tell me how many other non-hardware problems are
>> being reported under the heading "Segmentation fault"?
>
> Because you don't have permission to read the register?, maybe the
> error should be SIGILL, but I'm guessing that the linux fault handler
> doesn't know/care what produced the general protection trap.

Since it is a read (not a write) it could be allowed.
Maybe that would break DOSEMU or Wine. Is reading cr0 useful?

Next message: Andrew E. Mileski: "Re: 16 MB -> 32 MB, a memory problem resolved!"
Previous message: Zen: "I can't compile Kernel 1.3.83+"