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.
Need a way to log JDI calls - main goal is to be able to reproduce problems independently of NetBeans. At the moment we need it for stabilization of the debugger with FXJDI but it may be useful also for performance testing.
I can add logging to JDI wrapper classes - package org.netbeans.modules.debugger.jpda.jdi. The logging will work for all JDI methods called through debugger actions and API, with the exception of expression evaluation. If there is a need, it can be extended for the evaluation as well. But such logging will not work for JDI calls explicitly performed by JavaFX debugger directly on JDI objects. You'd have to add your own logging, specially if you use some javafx-specific JDI extensions.
FYI: To log JDWP traffic, you can also use https://jdwpanalyzer.dev.java.net/
Logging is added in changeset: 172928:30fc0438629e http://hg.netbeans.org/main/rev/30fc0438629e
Integrated into 'main-golden', will be available in build *201006150001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/30fc0438629e User: mentlicher@netbeans.org Log: #187445 - Allow logging of JDI method calls.
Please verify bugfix for this bug, so it can be included in release691 repository. Thanks, -R
verified
It looks like merge conflict for merging the changeset main #30fc0438629e into release691 repository. I've identified dependency on changeset main #df59fa0b7a46, namely change in file debugger.jpda/src/org/netbeans/modules/debugger/jpda/jdi/request/EventRequestManagerWrapper.java Please let me know the best approach for resolution of this merge conflict. I've got following options: #1 Mark issue 185431 with keyword 6.9.1_CANDIDATE and verify it on trunk #2 I can do partial port or changeset main #df59fa0b7a46, namely the part in file debugger.jpda/src/org/netbeans/modules/debugger/jpda/jdi/request/EventRequestManagerWrapper.java Ad #1) I will then transplant whole changeset main #df59fa0b7a46 into release691 repo, what will makes the changeset main #30fc0438629e cleanly applicable on transplant Ad #2) Partial changeset ports can be dangerous, especially in code clearly marked with comment "// DO NOT MODIFY THIS CODE, GENERATED AUTOMATICALLY" I need some to bless either of those options or suggest another option. Thanks, -R
I've prepared combined change in branch debugger_ports in release691 repository.
ported to release691 #e8181c0a7e5d
verified changes integrated into release691 clone