delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:6025 |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: go-32 and Linux DOSEMU |
Date: | Tue, 16 Jul 1996 00:01:54 CDT |
Organization: | Rice University, Houston, Texas |
Lines: | 9 |
Message-ID: | <31eb2242.sandmann@clio.rice.edu> |
References: | <199607151019 DOT GAA00705 AT fcshome DOT stoneham DOT ma DOT us> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
NNTP-Posting-Host: | clio.rice.edu |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
> big enough). I had gotten it to where it appeared to work, then I > constructed a 6-mb file for testing, and found that sometimes seemingly > benign commands caused a segmentation violation. Couldn't figure it out. > But when I upgraded to the new CWSDPMI the entire problem went away. Probably the insufficient internal heap bug in CWSDPMI. The default size was increased in r2 so you can now allocate up to around 20Mb of data in small pieces before badness. You can use CWSPARAM to bump it more if you need to edit 15Mb binary files :-)
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |