Xref: news-dnh.mv.net comp.os.msdos.djgpp:2088 Newsgroups: comp.os.msdos.djgpp Path: news-dnh.mv.net!mv!news.sprintlink.net!psgrain!usenet.eel.ufl.edu!col.hp.com!sdd.hp.com!spool.mu.edu!news.moneng.mei.com!news.ecn.bgu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!math.ohio-state.edu!magnus.acs.ohio-state.edu!lerc.nasa.gov!purdue!oitnews.harvard.edu!cfanews!cfa0!peprbv From: peprbv AT cfa0 DOT harvard DOT edu (Bob Babcock) Subject: Re: DPMI question Sender: news AT cfanews DOT harvard DOT edu Reply-To: rbabcock AT cfa DOT harvard DOT edu Organization: Smithsonian Astrophysical Observatory, Cambridge, MA, USA References: <4355ve$hj2 AT news DOT mountain DOT net> <43kpn0$1ji AT magus DOT cs DOT utah DOT edu> Date: Tue, 19 Sep 1995 05:10:16 GMT Lines: 12 To: djgpp AT sun DOT soe DOT clarkson DOT edu Dj-Gateway: from newsgroup comp.os.msdos.djgpp Steve Larsen (larsen AT lal DOT cs DOT utah DOT edu) 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. : Yeah, that is what I thought. However, according to the information : presented at the GPF, it is dying on the instruction that loads the : segment register. Very strange, I thought. My 80386 tech ref lists various possible causes for a GPF. Some of the possibilities include loading selectors (that are invalid in specific ways) into segment registers.