buffer overrun

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

Hans-Joachim Zierke wrote:
> Was will mir Herr/Frau mgetty denn hiermit sagen?

First, please talk English if you post to de.alt.comm.mgetty.  Just do it,
don't discuss it.

> 09/06 04:57:39 yS2  waiting for `CONNECT'' ** found **
> 09/06 04:57:53 yS2  send:
> 09/06 04:57:53 yS2  waiting for `_'' ** found **
> 09/06 04:57:54 yS2  buffer overrun - input prompt too long
> 09/06 04:57:54 yS2  buffer overrun - input prompt too long
> 09/06 04:57:54 yS2  buffer overrun - input prompt too long

Most likely, it means exactly this - the input prompt (or one or more
lines in /etc/issue, bad wording in the error message) expands to more
than 140 characters after all the escape sequences have been expanded.

To avoid dynamic memory management issues, the buffer has a fixed size,
but every strcat() is tested, and if the buffer fills, it will complain.

(Another possibility is that you found a mgetty bug :) -- please show your
mgetty.config, mgetty command line, and /etc/issue file).

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de