Path: utzoo!mnetor!uunet!husc6!linus!gatech!udel!mmdf From: Postmaster@locke.bitnet (PMDF Mail Server) Newsgroups: comp.os.minix Subject: Undeliverable mail Message-ID: <855@louie.udel.EDU> Date: 18 Dec 87 20:28:17 GMT Sender: mmdf@udel.EDU Lines: 47 The message could not be delivered to: Addressee: MINIX Reason: %MAIL-E, no such user MINIX at node LOCKE ---------------------------------------- Received: from JNET-DAEMON by locke.hs.washington.edu; Fri, 18 Dec 87 12:25 PST Received: From NDSUVM1(MAILER) by UWALOCKE with RSCS id 6295 for MINIX@UWALOCKE; Fri, 18 Dec 87 12:25 PST Received: by NDSUVM1 (Mailer X1.24) id 6257; Fri, 18 Dec 87 14:12:03 CST Date: 18 Dec 87 18:38:45 GMT From: Bing Bang Subject: Re: Problems with serial TTY driver Sender: Minix operating system To: Local Redistribution Reply-to: INFO-MINIX@UDEL.edu Comments: To: info-minix@UDEL.EDU In article <2314@encore.UUCP> paradis@encore.UUCP (Jim Paradis) writes: >After many weeks of not quite being able to get around to it, >I finally added serial line support to my rewritten MINIX TTY >driver. It works, but there's one serious problem: If I test >it out by looping back transmit and receive on the serial line >and running a quick&dirty terminal program, if I type at it >too fast the system will hang. Now, I remember someone else in >this newsgroup sometime back who added serial capabilities to >the stock TTY driver and ended up with the same problem. Is there well, i'm glad i'm not the only one having this problem. i've been trying to track this problem down for months. maybe we can team up. here's what i know of the problem. in tty_task, the message structure tty_mess is declared so that it is allocated on the stack. the problem seems to be that some routine corrupts 6 or 8 bytes just below the address of the structure. this of course usually contains the reuturn address and stuff from the receive() call tty_task makes. i know the corruption is relative to the structure address becuse i can make other declarations in tty_task to move the location of the structure. the problem can be "solved" by allocating a char array just below the structure, although memory in the array still get corrupted. i do not care for this solution. -- Bing H. Bang +----------------------------------------------------+ Harris/Lanier |MSDOS and OS/2 (whenever it gets here): just say no.| Atlanta GA +----------------------------------------------------+