This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 18508 - when running debugger, output window did not properly output results of System.out.print() call, or echo input to the window after reading it from the input box.
Summary: when running debugger, output window did not properly output results of Syste...
Status: RESOLVED DUPLICATE of bug 56341
Alias: None
Product: platform
Classification: Unclassified
Component: Output Window (show other bugs)
Version: 5.x
Hardware: PC Unix
: P3 blocker (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-10 19:53 UTC by jmorgan
Modified: 2008-12-22 09:49 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
a project to reproduce the issue on NetBeans 5.5 (6.87 KB, application/octet-stream)
2006-11-23 20:36 UTC, rosti
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jmorgan 2001-12-10 19:53:40 UTC
Netbeans 3.2.1 build 98, JDK 1.3.1_01
when running debugger in Netbeans 3.2.1 on a Pentium IIIM 1.13 ghz running 
Windows XP professional and a month-old build of JDK 1.3.1_01, output window 
did not properly output results of System.out.print() call, or echo input to 
the window after reading it from the input box.  The program I was debugging 
had two threads, one doing all the work and user-interaction, and one listening 
on a TCP ServerSocket.  The UI portion would present a prompt, then let the 
user enter commands.  The prompt was generated using System.out.print().  It 
looks like there is code in the output window to only flush the output buffer 
to the display on newlines.  The prompts would eventually be displayed, once a 
System.out.println() was called, but not before.  The input I entered was never 
echoed on the output window, and the readline's end of line was not counted, 
and so did not progress the output cursor to the next line, making reading and 
parsing the output very difficult.  Input and output worked fine from the 
Windows XP command prompt.  This issue was accompanied by other issues that 
were much more difficult to reproduce consistently (and I quit debugging in 
frustration instead of fleshing them out so I could report them), including the 
step over button beginning to have the effect of continuing execution instead 
of going to the next statement, and multi-threaded access exceptions ( I am on 
a different computer, or I would list the exact exception - it only takes a few 
executions to incapacitate the debugger ).  I did at times use the stop 
execution button to stop the process I was debugging in the middle of its 
execution.  This was necessary sometimes when the debugger would, after I 
clicked the continue button, go away and never come back.  I could, of course, 
not see whether a new prompt had displayed or not, so I would type a few lines, 
see no response, then stop the process.  The debugging process's thread also 
committed an illegal operation in Win XP three times in a 6 hour span, 
prompting windows Xp to report to the Microsoft mothership with a bug report.
Comment 1 Jan Jancura 2001-12-11 17:37:24 UTC
Hello Jonathan,
problems with System.out.print() & input are fixed in NetBeans 3.3.
Can you test our RC1, please? 

Regarding other problems, can you create separate issues with step-by
step description how to reproduce it? The main proble is that NB is
not tested on Win XP well. 
Thanks for your report.
Comment 2 Jan Jancura 2001-12-17 10:08:11 UTC
fixed in release33, release330
Comment 3 Jan Stola 2002-01-04 15:08:05 UTC
Verified in Netbeans build 20020104.
Comment 4 Quality Engineering 2003-06-30 17:28:18 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 5 rosti 2006-11-23 20:34:52 UTC
I'm experiencing the same problem on FreeBSD 6.2-PRERELEASE with netbeans-5.5
and diablo-jdk-1.5.0.07.01_1 builded and installed from the FreeBSD ports
collection. My computer is also a Pentium III based one.

I will attach a project for reproducing this issue. Try to debug it on NetBeans
5.5 by pressing F7 and check an output in the output window.
Comment 6 rosti 2006-11-23 20:36:19 UTC
Created attachment 36257 [details]
a project to reproduce the issue on NetBeans 5.5
Comment 7 Martin Entlicher 2007-01-08 09:19:54 UTC
This is a problem in the terminal emulator. The same behavior is without
debugger when Run is executed.
Comment 8 ivan 2007-01-08 19:45:28 UTC
Since 4.x the terminalemulator is no longer part of the output mechanism.
This is likely to be an ant io problem.
Comment 9 Milos Kleint 2007-01-09 08:57:22 UTC
in post 4.x version, ant is responsible to pumping the output to the OW.
unfortunately it does so on a per-line basis.


duplicate of #56341

*** This issue has been marked as a duplicate of 56341 ***