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 112670 - RubyDebuggerException (timeout) when trying to evaluate 'sleep'
Summary: RubyDebuggerException (timeout) when trying to evaluate 'sleep'
Status: RESOLVED DUPLICATE of bug 101120
Alias: None
Product: ruby
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Krauskopf
URL:
Keywords:
Depends on: 101120
Blocks:
  Show dependency tree
 
Reported: 2007-08-13 16:21 UTC by Tomas Danek
Modified: 2007-09-18 08:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
log (14.88 KB, text/plain)
2007-08-13 16:22 UTC, Tomas Danek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Danek 2007-08-13 16:21:17 UTC
20070813
-----------
ruby+classic debugger

code:

require('thread')

a = Thread.start{
  puts "aaaaaaaaaaaaa"
}
b = Thread.start{
  puts "bbbbbbbbbb"
}
puts "ccc"
sleep

2 breakpoints, on each puts in thread.
started debugger, debugger stopped at puts "aaaaaaaaa". Pushed F8 (probably more times), nothing happened. Invoked
threads view, got the exception: 

org.rubyforge.debugcommons.RubyDebuggerException: Unable to read information in the specified timeout [10s]
        at org.rubyforge.debugcommons.ReadersSupport.readInfo(ReadersSupport.java:143)
        at org.rubyforge.debugcommons.ReadersSupport.readFrames(ReadersSupport.java:158)
        at org.rubyforge.debugcommons.RubyDebuggerProxy.readFrames(RubyDebuggerProxy.java:293)
        at org.rubyforge.debugcommons.model.RubyThread.getFrames(RubyThread.java:27)
...

attaching full log.


        at org.rubyforge.debugcommons.model.RubyThread.getTopFrame(RubyThread.java:40)
Comment 1 Tomas Danek 2007-08-13 16:22:09 UTC
Created attachment 46518 [details]
log
Comment 2 Martin Krauskopf 2007-08-14 12:28:00 UTC
It is because of evaluation of 'sleep'. Might be fixed somehow in the backend. E.g. run evaluation in separate thread
and give up after ten seconds. Should be fixed in 6.0 time frame.
Comment 3 Martin Krauskopf 2007-09-18 08:37:54 UTC
Actually dupe of 101120. There is already 10s timeout (to prevent never-ending wait). It is similar to try to evaluate
'exit'.

*** This issue has been marked as a duplicate of 101120 ***
Comment 4 Martin Krauskopf 2007-09-18 08:40:57 UTC
Also note that it is unlikely that it happens to you again after issue 112662 was fixed. Actually the issue 112662 was
probably the reason why 'sleep' was evaluated. Should not happen anymore.