Importing Default project from 321 throws exceptions. Exception and System dir
Created attachment 4894 [details]
exceptions stack traces
Created attachment 4895 [details]
zipped system dir with Default project
IMHO two problems: OutputTab.Replace (core/term) and the other
(debuggercore/code). Not sure though.
Yes it seems so.
Please who is responsible for "Threads","Session"? Debuggercore module?
Yes. "Threads" and "Sessions" are part of the Debugger Window - part
of Debugger Core.
The "SafeException" is thrown from
org.openide.explorer.ExplorerManager during deserialization of UI
- a list of debugging sessions
- a list of threads
ExplorerManager has four persisent fields (both in NB 3.2.1 and in the
current dev. build):
- Node.Handle root
- String rootName
- String explored
- Object selected
Field "root" is the only important field - it must not be null during
serialization. If it is null, the SafeException is thrown during
I debugged both serialization (in NB 3.2.1) and deserialization (in
the current dev. build). Serialization seems to be correct -
ExplorerManager.writeObject(...) saves non-null value to field "root".
But somehow this field is null during deserialization in the dev. build.
I was told that there is some tools for analysis of serialized data. I
will try it.
Increasing priority, by definition.
I see only evaluation of debugger part of the problem, but who could
say something about OutputTab.Replace problem. Or should I file
another bug for it?
The problem with "Threads" and "Sessions" is that classes
"SessionThreadRootNode$SessionHandle" have been moved from package
"~.debugger.multisession.nodes" to "~.debugger.support.nodes" (between
NB 3.2.1 and NB 3.3).
Unfortunately, exceptions ClassNotFoundException (that must be
generated during deserialization in this case) are caught during
deserialization so it is quite difficult to find a cause of a problem.
Fixed problems with root nodes "Threads" and "Sessions" (class names
are now translated during project deserialization).
Problem with deserialization of "OutputTab.Replace" is probably in
core (so I change the "Component" status of this bug).
Ales, please investigate. It can be in the output window or the
window system itself.
It's in output window.
Also "OutputTab.Replace" part fixed in trunk,
so marking as FIXED
we may want to integrate this fix into 3.3.2. Added 3.3.2_CANDIDATE
Core part of problem (OutputTab.Replace) doesn't appear in 3.3.1,
so it isn't 3.3.2 candidate from Core perspective.
I'm changing component back to debugger.
Debugger part of problem (OutputTab.Replace) doesn't appear in 3.3.1,
so it isn't 3.3.2 candidate from Debugger perspective.
Verified in dev-200203150100.
Resolved for 3.3.x or earlier, no new info since then -> closing.