On 0, Darren Salt <[EMAIL PROTECTED]> wrote:
> I demand that Anthony DeRobertis may or may not have written...
>
> [snip]
> > Writing off of allocated memory causes a page fault as well
>
> Well, I suppose that that would be useful if the memory is unrepairable... I
> hope that it was insured :
I demand that Anthony DeRobertis may or may not have written...
[snip]
> Writing off of allocated memory causes a page fault as well
Well, I suppose that that would be useful if the memory is unrepairable... I
hope that it was insured :-)
--
| Darren Salt| nr. Ashington, |
On 0, Anthony DeRobertis <[EMAIL PROTECTED]> wrote:
[snip]
> > A page fault, despite its name, has nothing to do with
> > memory corruption or an invalid access.
>
> It has quite a bit to do with an invalid access. As far as the MMU is
> concerned, it *is* an invalid access: There is no page map
also sprach Anthony DeRobertis <[EMAIL PROTECTED]> [2002.09.26.1322 +0200]:
> > i am repeatedly seeing the term "page fault" being used in Debian in
> > the wrong way.
>
> (examples?)
libsigsegv-dev's description
various posts to the debian-* lists
> It has quite a bit to do with an invalid acc
On Thu, 2002-09-26 at 04:50, martin f krafft wrote:
> i am repeatedly seeing the term "page fault" being used in Debian in
> the wrong way.
(examples?)
> A page fault, despite its name, has nothing to do with
> memory corruption or an invalid access.
It has quite a bit to do with an invalid ac
5 matches
Mail list logo