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 190986 - No debugger output in console when suspending/resuming threads
Summary: No debugger output in console when suspending/resuming threads
Status: VERIFIED DUPLICATE of bug 166616
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.0
Hardware: PC Linux
: P4 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-13 16:46 UTC by Jiri Kovalsky
Modified: 2011-01-24 12:07 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Kovalsky 2010-10-13 16:46:00 UTC 
Product Version: NetBeans IDE 7.0 M2 (Build 201010121358)
Java: 1.6.0_22; Java HotSpot(TM) Client VM 17.1-b03
System: Linux version 2.6.31-22-generic running on i386; UTF-8; en_US (nb)
Userdir: /home/cesilko/.netbeans/7.0m2

Description:
============
When user stops or resumes a thread in Debugging explorer, nothing is printed into the Debugger Console tab in the Output window. Instead, messages like Thread Thread-1 stopped at Thread.java.sleep" should be printed there.

Steps to reproduce:
===================
1. Launch NetBeans 7.0 development build with empty userdir.
2. Via "File > New Project..." create Anagram Game sample Java application project.
3. Invoke "Window > Debugging > Debugging" from main menu.
4. Right click the project node and invoke "Debug" from its popup menu.
5. Right click "AWT-EventQueue-0 running" node in Debugging explorer and choose "Suspend" from its popup menu.
6. Look into Debugger Console tab of the Output window that it only contains the following two lines: "Listening on <port>" and "User program running".
Comment 1 Martin Entlicher 2011-01-22 00:22:29 UTC 
This is actually a duplicate of issue #166616.

*** This bug has been marked as a duplicate of bug 166616 ***
Comment 2 Jiri Kovalsky 2011-01-24 12:07:22 UTC 
Yes, you are right. Verifying as duplicate. My bad.