Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!rutgers!husc6!seismo!vrdxhq!vsedev!ron From: ron@vsedev.VSE.COM (Ron Flax) Newsgroups: net.unix-wizards Subject: Microport Unix -- Large Model Problems Message-ID: <188@vsedev.VSE.COM> Date: Wed, 29-Oct-86 11:14:11 EST Article-I.D.: vsedev.188 Posted: Wed Oct 29 11:14:11 1986 Date-Received: Thu, 30-Oct-86 07:27:14 EST Reply-To: ron@vsedev.VSE.COM (Ron Flax) Distribution: net Organization: VSE Software Development Lab Lines: 30 Keywords: Microport, Unix, Memory, Segmentation Has anyone else out there been experiencing problems with porting programs to Microport Unix V/AT that fall into the large model category? It seems that most everything I port (try to port?) has pointer alignment problems, as indicated by lint, or just core dumps with a segmentation violation at strange places in the code, like on a strlen() call? Sdb seems to indicate a memory fault as the culprit and I think that most of the problems are pointer related since an 'int' ain't necessarily an 'int' (ie. 16 bits in small model, 32 bits in large model). Does anyone have any words of wisdom as to how one might go about fixing pointer alignment problems without too much pain? One other unrelated problem I have with Microport Unix is that for one reason or another the system seems to run for a while then when it decides its had enough it just plain goes south. It appears to be a deadlock situation since terminals that had active sessions going continue to echo keystroke even though it doesn't respond to them and non-active sessions (ie. getty's running) do NOT echo keystrokes. This obviously quite annoying as you might imagine... One other thing that is interesting is that I know of two other sites with the exact same problem on different hardware, but Microport claims they have never heard of it? Has anyone else seen this behavior? Incidentally I was running SCO Xenix V successfully for about 6 months prior to getting Microport Unix. Microport are you listening 8-) -- ron@vsedev.VSE.COM (Ron Flax) UUCP: ..!seismo!vsedev!ron ARPA: vsedev.VSE.COM!ron@seismo.CSS.GOV