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 238897 - [nashorn] Debugger sometimes leaves no other option than to stop debugging
Summary: [nashorn] Debugger sometimes leaves no other option than to stop debugging
Status: NEW
Alias: None
Product: javascript
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 8.0
Hardware: PC Linux
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-27 15:47 UTC by Vladimir Riha
Modified: 2014-01-07 13:30 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
IDE log (91.59 KB, text/plain)
2013-11-27 15:47 UTC, Vladimir Riha
Details
thread dumps (17.02 KB, application/zip)
2013-11-27 15:48 UTC, Vladimir Riha
Details
screenshot (94.59 KB, image/png)
2013-11-27 15:49 UTC, Vladimir Riha
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Riha 2013-11-27 15:47:41 UTC
Created attachment 142647 [details]
IDE log

Please check this screenshot, debugging is paused on the first line but I have no other option than to Stop debugging, other controls are disabled. It happened when I had following Java code:


...
engine.eval("function hi(){\nvar a = 'PROSPER'.toLowerCase(); \nmiddle(); \nprint('Live long and' + a)}\n function middle(){\n var b = 1; for(var i=0, max = 5; i<max;i++){\nb++;\n}\n print('b is '+b);}");
...




now on this line with engine.eval(), I had line breakpoint and once it was hit, I pressed Step Into twice, at this moment <eval>.js was opened with debugger paused at the first line, so I pressed Step Into. And now the only option I can do is to stop debugging. I'm attaching 3 thread dumps taken ~25 sec apart each other.

It is not always reproducible, but it happen very often


Product Version: NetBeans IDE Dev (Build 201311270002)
Java: 1.8.0-ea; Java HotSpot(TM) Client VM 25.0-b59
Runtime: Java(TM) SE Runtime Environment 1.8.0-ea-b117
System: Linux version 3.2.0-48-generic-pae running on i386; UTF-8; en_US (nb)
Comment 1 Vladimir Riha 2013-11-27 15:48:39 UTC
Created attachment 142648 [details]
thread dumps
Comment 2 Vladimir Riha 2013-11-27 15:49:51 UTC
Created attachment 142650 [details]
screenshot
Comment 3 Vladimir Riha 2013-11-27 17:19:45 UTC
It really happens a bit often, also basically all debugger-related windows (like Call stack, Variables, Breakpoints) are then stuck on "please wait"
Comment 4 Martin Entlicher 2014-01-07 07:52:57 UTC
The thread dump shows, that there is some watch being evaluated. But the watch evaluation does not end. This is why the debugger can not proceed with anything.
Can you recall what expression do you have in watches?
Reducing to P3 for now. This does not seem to be a real bug in debugger implementation...
Comment 5 Vladimir Riha 2014-01-07 08:27:11 UTC
I don't remember but I'll try to find it out during this week.
Comment 6 Vladimir Riha 2014-01-07 13:30:10 UTC
Using the snippet from description, to reproduce please try:

 - add line breakpoint to line with engine.eval()
 - debug project
 - once it stops on engine.eval(), press Step Into twice so debuggers stops on 1st line of <eval>
 - add following 2 watches:
   a
   b
 - finish debugging
 - debug project
 - once it stops on engine.eval(), press Step Into twice so debuggers stops on 1st line of <eval>
 - press Step Into

=> now you can only finish debugging. It seems like you need both watches to reproduce it.



Product Version: NetBeans IDE Dev (Build 201401060002)
Java: 1.8.0-ea; Java HotSpot(TM) Client VM 25.0-b65
Runtime: Java(TM) SE Runtime Environment 1.8.0-ea-b122
System: Linux version 3.2.0-48-generic-pae running on i386; UTF-8; en_US (nb)