The output window does not allow to type input for the program and it features only minimal terminal emulation: \n (line-feed) is treated like a carriage-return-line-feed combination, and \r (carriage-return) is ignored. These capabilities are usually sufficient to debug GUI programs which only write debugging output to stdout and stderr.
When a program is debugged with KDbg for the first time, the program output window is not used. The reason for this is that KDbg cannot know whether the program requires sophisticated terminal emulation or if it expects input through a terminal. So, a terminal emulator program is used by default. In order to redirect the output to the output window, you must do the following:
If the last line of the output is visible, the window always scrolls automatically so that the last line remains visible when new output arrives.. If, however, you manually scroll up so that the last line is not visible, the visible portion of text will not change.