Sorry, but this can not be a defect. Debug tab is a concept used from the beginning of debugger and if we're supposed to
replace it with something else, it would require some UI redesign.

Debug Tab concept is OK, but it should be possible to disable it. Information printed is not usually needed. If user
sets invalid breakpoint he can see it immediately in editor, there is no need to print such information to tab. Opening
many OW tabs without any useful content is rather annoying for users (check issue 103190). It would be nice to be able
to disable it for those who are not interested.

We were discussing this topic and decided following solution:

Debugger Console will not open unless there's some problem (printed in red text). When a red text is printed, the
Debugger Console opens and becomes visible (like now). It will stay opened till the end of the debugger session and
again open on on errors in the next session.

There will be Window -> Debugging -> Debugger Console menu item. When activated, the Debugger Console will open. It will
keep open from that on in every session by default until explicitly closed.

I believe that it's important to be notified about broken breakpoints this way, since you're surely not watching all
breakpoints in Editor. The breakpoint can become invalid at unpredictable times, therefore explicit notification is
necessary.

Please let me know if you have any comments on this, I'm starting to work on it...

You can see invalid breakpoints in Breakpoints window. I think it should be possible to suppress debug tab no matter
what is written into it. If something does not work one can enable it and investigate.

One can surely investigate. Or be notified about the problem.
In the past we had many complaints about non-working breakpoints. Therefore I've added breakpoint validity and warn
users about invalid breakpoints. IMHO invalid breakpoints should be an exceptional state. You want your breakpoint to
work. Therefore when there are broken breakpoints, you should fix them or delete them. You can ignore them as well, but
in my opinion it's more important to warn users about invalid breakpoints when they want they want them to work, than
disturb users that do not care.

FYI: I've submitted issue #161773 for a better solution, which we discussed.

User should decide himself if he is interested or not. You want to make decision for him. Opening useless tabs is
annoying for users and debugger tab was mentioned by users as one of the useless in CA survey. I never used information
in debugger tab (editor + Breakpoints window shows valid/invalid/disabled breakpoints already). If you are so sure that
most people want and need information written to debugger tab you can leave it enabled by default but there _should_ be
an option to disable it.

O.K. Since I've found that there's no API for opening/closing of InputOutput, I'll add the option to hide the Debugger
Console.

Option added in changeset:   125091:2df9f9a3dff9
http://hg.netbeans.org/main/rev/2df9f9a3dff9

Integrated into 'main-golden', will be available in build *200904040200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/2df9f9a3dff9
User: mentlicher@netbeans.org
Log: #160875 - Option for opening Debugger Console introduced.

Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.

I'm using Netbeans 8.2 and I don't see the resolution suggested by Martin Entlicher  in the third comment.

Thanks, best regards

It is in Tools -> Options, select "Java" and "Java Debugger" tab.
In the "General" category it's the second option from the bottom:
"Open Debugger Console for debugging session"

Ok thank you very much