delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1995/09/14/19:05:46

Xref: news-dnh.mv.net comp.os.msdos.djgpp:2041
Path: news-dnh.mv.net!mv!news.sprintlink.net!in2.uu.net!tcsi.tcs.com!agate!islay.ssl.berkeley.edu!korpela
From: korpela AT islay DOT ssl DOT berkeley DOT edu (Eric J. Korpela)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DPMI question
Date: 14 Sep 1995 20:45:20 GMT
Organization: Cal Berkeley-- Space Sciences Lab
Lines: 17
References: <DEt18B DOT HsB AT jade DOT mv DOT net> <4355ve$hj2 AT news DOT mountain DOT net>
Nntp-Posting-Host: islay.ssl.berkeley.edu
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

In article <4355ve$hj2 AT news DOT mountain DOT net>,
grinch AT access DOT mountain DOT net <Sherm Pendley> wrote:
>This deserves some elaboration.  Loading an invalid value into a segment
>selector shouldn't cause a GP fault.  Attempting to access a segment
>through a selector which contains an invalid value does cause a fault.

I thought that the segment base and limit (invisible) registers were loaded 
from the LDT or GDT when the segment register is modified.  If that causes
a read past the limit of the GDT or LDT, shouldn't the processor generate an
exception?

Eric
-- 
Eric Korpela                        |  An object at rest can never be
korpela AT ssl DOT berkeley DOT edu            |  stopped.
<a href="http://www.cs.indiana.edu/finger/mofo.ssl.berkeley.edu/korpela/w">
Click here for more info.</a>

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019