Date: Sun, 3 Aug 1997 11:21:47 -0400 From: Charles Henrich <henrich@crh.cl.msu.edu> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: tom@sdf.com, freebsd-hackers@FreeBSD.ORG Subject: Re: tty-level buffer overflows Message-ID: <19970803112147.21483@crh.cl.msu.edu> In-Reply-To: <199708030852.SAA13473@genesis.atrad.adelaide.edu.au>; from Michael Smith on Sun, Aug 03, 1997 at 06:22:34PM %2B0930 References: <19970803025730.57257@crh.cl.msu.edu> <199708030852.SAA13473@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On the subject of Re: tty-level buffer overflows, Michael Smith stated:
> > Not in this case, its a 16550A, on a 486/66 doing absolutely nothing
> > except trying to do filetransfer over the serial port with a custom app I
> > wrote..
>
> And of course if you bothered to read the sio(4) manpage it would tell you
> what the error message means. Or if you'd mentioned that you're using a
Ooh, arent we high and mighty. I did read the man page, one line that says
"The application is broken" is about as useless as it gets. As my original
message said, I've waded through all the message archives searching for an
anaswer, Im not about to waste peoples time without having spent a
considerable amount of effort attempting to figure it out on my own.
> Your application is busted; data is arriving faster than your app is reading
> it, and the kernel has run out of patience and started throwing the data
> away.
Im afraid not, the application is a software Upload, with a singly byte ack
every 2k, if the serial port cant handle that, theres a problem. I would
presume that if the buffer is full, a write() should block.
-Crh
Charles Henrich Michigan State University henrich@msu.edu
http://pilot.msu.edu/~henrich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970803112147.21483>