Debugger: Only add java specific InlineValueComputerImpl for JPDA sessions#9073
Merged
matthiasblaesing merged 1 commit intoapache:masterfrom Dec 13, 2025
Merged
Conversation
…sions Observed exception: java.lang.NullPointerException: Cannot invoke "org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.addPropertyChangeListener(java.beans.PropertyChangeListener)" because "this.debugger" is null at org.netbeans.modules.debugger.jpda.ui.models.InlineValueComputerImpl.(InlineValueComputerImpl.java:101) at org.netbeans.modules.debugger.jpda.ui.models.InlineValueComputerImpl$Init.sessionAdded(InlineValueComputerImpl.java:306) [catch] at org.netbeans.api.debugger.DebuggerManager.fireSessionAdded(DebuggerManager.java:1324) at org.netbeans.api.debugger.DebuggerManager.addSession(DebuggerManager.java:1598) at org.netbeans.api.debugger.DebuggerManager.startDebugging(DebuggerManager.java:314) at org.netbeans.modules.cpplite.debugger.CPPLiteDebugger.startDebugging(CPPLiteDebugger.java:845) at org.netbeans.modules.cpplite.debugger.api.Debugger.startInDebugger(Debugger.java:43) at org.netbeans.modules.cpplite.project.ActionProviderImpl.lambda$invokeAction$4(ActionProviderImpl.java:88) at org.netbeans.api.extexecution.base.BaseExecutionService$2.call(BaseExecutionService.java:236) at org.netbeans.api.extexecution.base.BaseExecutionService$2.call(BaseExecutionService.java:212) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1403) at org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45) at org.openide.util.lookup.Lookups.executeWith(Lookups.java:287) at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2018)
Contributor
Author
|
@scalyon please test the nightly build available from the checks page (or directly: https://github.com/apache/netbeans/suites/51723620523/artifacts/4802105448). @lahodaj could you please have a look? I think this is caused by the addition of the inline value display for java debugging. I think the fix is trivial. |
lahodaj
approved these changes
Dec 10, 2025
Contributor
lahodaj
left a comment
There was a problem hiding this comment.
Looks good to me, thanks!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Exceptions can be observed with CPPLite and JS debugger. The issue is that the support for showing values for variables inline is registered unconditionally, but the implementation is JPDA only.