2023 Feb 23 8:33 AM
Hello folks,
I was using Eclipse 2022-09 and ADT Version 3.28. Debugger was working fine for a long time and I was able to debug the RFCs (moving from one SAP system to another).
However, yesterday I upgraded to Eclipse 2022-12 and ADT Version 3.32 (The JRE version also upgraded to 17 in the process). Since then, while the debugger is working fine, but while debugging RFC and moving into another system, the debugger fails and shows 'source not found'.
I also tried doing 'Edit Source Lookup Path' and adding the other system as an ABAP project in the Lookup Path, but it still doesn't work.
It should not be a problem with the Backend SAP system itself, because it was working fine earlier. Please help resolve the issue.
2023 Mar 02 11:27 AM
Hello Ravi,
the release of an ADT update via the update site is planned for the next days.
Please check with the new released ADT version whether the bug is fixed.
Best regards,
Denis Ungemach
2023 Feb 27 8:48 AM
I did a fresh install of Eclipse for Java Developers 2022-12, with just ADT Latest Plugin and nothing else. The problem still persists.
Below is the Error log details, if it helps :
eclipse.buildId=4.26.0.20221201-1200
java.version=17.0.5
java.vendor=Eclipse Adoptium
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.java.product -product org.eclipse.epp.package.java.product -product org.eclipse.epp.package.java.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product -product org.eclipse.epp.package.java.product -data file:/C:/Users/RS/Development/eclipse/eclipse-2022-12/eclipse-workspace/ -product org.eclipse.epp.package.java.product
org.eclipse.debug.core
Error
Mon Feb 27 14:05:17 IST 2023
Problems occurred when invoking code from plug-in: "org.eclipse.debug.core".
java.lang.NullPointerException: Cannot invoke "java.net.URI.toString()" because "this.baseUri" is null
at com.sap.adt.debugger.internal.data.AbapDebugStackEntry.getBaseVitUri(AbapDebugStackEntry.java:220)
at com.sap.adt.debugger.internal.model.AbapDebugStackFrame.getBaseVitUri(AbapDebugStackFrame.java:1349)
at com.sap.adt.debugger.internal.model.AbapDebugStackFrame.getSourceCode(AbapDebugStackFrame.java:328)
at com.sap.adt.debugger.internal.AbapDebuggerVitFileManager.getOrCreateFileFromDebuggerForStackFrame(AbapDebuggerVitFileManager.java:127)
at com.sap.adt.debugger.internal.sourcelookup.AbapSourceLookupParticipant.getSourceName(AbapSourceLookupParticipant.java:105)
at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupParticipant.findSourceElements(AbstractSourceLookupParticipant.java:58)
at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector$SourceLookupQuery.run(AbstractSourceLookupDirector.java:138)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector.doSourceLookup(AbstractSourceLookupDirector.java:473)
at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector.getSourceElement(AbstractSourceLookupDirector.java:714)
at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.lookup(SourceLookupFacility.java:303)
at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility$SourceLookupTask.run(SourceLookupFacility.java:752)
at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility$SourceLookupJob.run(SourceLookupFacility.java:690)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
2023 Feb 28 10:47 AM
Hello Ravi,
thanks for reporting the bug and adding the error log. I think we found a fix for the issue.
I keep you up to date.
Best regards,
Denis Ungemach
2023 Mar 02 11:27 AM
Hello Ravi,
the release of an ADT update via the update site is planned for the next days.
Please check with the new released ADT version whether the bug is fixed.
Best regards,
Denis Ungemach
2023 Mar 02 8:22 PM
I have the same problem. Can you accelerate correction for this bug?
2023 Mar 03 3:34 PM
Hi Denis,
I updated to ADT 3.32.2 today on both fresh install and upgraded version of Eclipse 2022-12.
I can confirm you that i am able to debug the RFC by navigating from one system to another in the ADT debugger. Thank you!
For reference this is the current versions installed in my system :