From: Michael Bukin Newsgroups: comp.os.msdos.djgpp Subject: Re: What's Broken in Windows DPMI Date: 08 Apr 1999 00:39:20 +0700 Organization: Budker Institute of Nuclear Physics Lines: 32 Message-ID: <20lng45nzr.fsf@Sky.inp.nsk.su> References: <20soaep24u DOT fsf AT Sky DOT inp DOT nsk DOT su> NNTP-Posting-Host: sky.inp.nsk.su X-Newsreader: Gnus v5.5/Emacs 19.34 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com I have cleaned up some tests and placed them here: http://www.jado.org/users/bukinm/trace/index.html If there are problems with compiling files with Borland C, I can place sample log files somewhere. These tests also can show problem with bash. bash is deallocating LDT descriptors several times. To Martin: if you don't test that descriptor was deallocated already, then you can place second copy of selector to the list of free descriptors and then return two selectors pointing to one descriptor, pretending that they are pointing to different descriptors. That might give you problems too. Michael Bukin writes: > Eli Zaretskii writes: > > > How much memory does the allocation request? If it's not much, you > > might not notice it. > > BX=0x0800 in call to Int 0x21/AH=0x48, so I think it is 0x800 > paragraphs, but I don't have my test logs or interrupt list on that > computer (will post complete information with test program later). Sorry, this information is also incorrect. It is allocating 0x29 paragraphs in stub.asm. It allocates private data for DPMI host. -- Michael Bukin