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 71263 - 'User program finished' not printed to output
Summary: 'User program finished' not printed to output
Status: VERIFIED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Daniel Prusa
URL:
Keywords: T9Y
Depends on:
Blocks:
 
Reported: 2006-01-11 11:47 UTC by Jiri Skrivanek
Modified: 2008-05-20 15:30 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Debug messages (3.77 KB, text/plain)
2006-01-11 11:48 UTC, Jiri Skrivanek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2006-01-11 11:47:07 UTC
Although it seems trivial, it is vital for automated tests. When I Finish
Debugger Session I need to know that debugger really finished. That's why I wait
for message "User program finished". But it is not printed out sometimes. It is
because DebuggerOutput.destroy() is called before property change of
JPDADebugger.STATE_DISCONNECTED is fired. Trying to investigate it why I found
out that JPDADebuggerImpl.finish is called by two threads from
StartActionProvider.java:224 and KillActionProvider. Please, look at attached
log messages. It shows these two concurrent threads and property change
STATE_DISCONNECTED is never called. Could it be somehow synchronized or fixed a
different way? These issues might be also interesting: 44412, 56233.

I reproduced it also manually:

- create web project
- set Swing HTML browser as default
- add breakpoint to index.jsp
- start debugger and wait until it stops at breakpoint
- call Continue from main menu
- quickly after previous action call Finish Debugger Session from main menu.
Debugger seems to be stopped but "User program finished" message is never displayed.

Build 20060111-0429, JDK1.5.0_06, WindowsXP.
Comment 1 Jiri Skrivanek 2006-01-11 11:48:04 UTC
Created attachment 28346 [details]
Debug messages
Comment 2 Martin Entlicher 2006-02-10 15:32:06 UTC
I was able to reproduce this. Thanks for the analysis, it helps.
Comment 3 Peter Pis 2008-04-10 22:54:35 UTC
Changing TM for open issues.
Comment 4 Daniel Prusa 2008-05-20 12:05:24 UTC
Already fixed, inspecting the related code, StartActionProvider and KillActionProvider seems to be synchronized now. No
longer reproducible.
Comment 5 Jiri Skrivanek 2008-05-20 15:30:50 UTC
Verified.