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 50873 - JDI exceptions
Summary: JDI exceptions
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2004-10-26 21:45 UTC by Jesse Glick
Modified: 2010-04-29 09:19 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Stack traces found in my log file (10.27 KB, text/plain)
2004-10-26 21:45 UTC, Jesse Glick 		Details
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 Jesse Glick 2004-10-26 21:45:10 UTC 
041026 custom, 1.5.0. I have been trying to debug
a unit test (AntGrammarTest) for a while, with
only occasional success. Sometimes the process
starts but doesn't seem to do anything for a while
(I have a conditional breakpoint set in a place it
has to encounter); sometimes setting "main" as the
current thread makes it break, sometimes not.
Suspend/Resume on "main" don't seem to do anything
(does not give me a call stack). Sometimes I have
a current line cursor, and I press F8 in the
middle of a long method, on a call which should
complete very quickly, but I do not get the
current line back - just nothing happens, and
Suspend does nothing.

Not sure what is going on, but I found some
exceptions in my log file.
Comment 1 Jesse Glick 2004-10-26 21:45:54 UTC 
Created attachment 18534 [details]
Stack traces found in my log file
Comment 2 Jan Jancura 2004-10-27 17:28:09 UTC 
Is it reproducible? Can you attach testcase. I am not sure whats
happening there from your log.
Comment 3 Jesse Glick 2004-10-27 21:50:03 UTC 
Don't think it's reproducible. However it seems that at the time I was
trying to use classes for which the debugger had no configured sources
(since the classes were loaded dynamically).

Could be closed if you can't do anything at all with it, but ideally
the NB debugger should try to annotate such problems with information
about what was going on and why JDI might have failed, so it could be
fixed in the future - either on the NB side or in the JDK, as appropriate.

I should mention that it is very common for me to see this kind of
exception in my log file whenever I try to use the JPDA debugger.
Comment 4 Jan Jancura 2005-02-16 12:44:24 UTC 
Fixed in main trunk:


Checking in JPDADebuggerImpl.java;
/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/JPDADebuggerImpl.java,v
 <--  JPDADebuggerImpl.java
new revision: 1.61; previous revision: 1.60
done
Comment 5 Quality Engineering 2010-04-29 09:19:49 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.