Eclipse Community Forums: Newcomers » Problem with Debugging in ADT (ABAP Development Tool) on Eclipse 2022-12

Home » Newcomers » Newcomers » Problem with Debugging in ADT (ABAP Development Tool) on Eclipse 2022-12

Problem with Debugging in ADT (ABAP Development Tool) on Eclipse 2022-12 [message #1857730]

Thu, 23 February 2023 02:32

Eclipse User

Hi,

I was using Eclipse 2022-09 and ADT Version 3.28. It was working fine for a long time and I was even 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 versin also upgraded to 17 in the process). Since, then while the debugger is working fine, while debugging RFC and moving into another system, the debugger fails and shows 'source not found'. (Please see attached screenshot).

I also tried doing 'Edit Source Lookup Path' and additing 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 find the issue.

Attachment: Source Not found.png
(Size: 13.92KB, Downloaded 245 times)

Re: Problem with Debugging in ADT (ABAP Development Tool) on Eclipse 2022-12 [message #1857733 is a reply to message #1857730]

Thu, 23 February 2023 04:12

Eclipse User

You should really look to the provider of these tools for help. From where did you get them?

Re: Problem with Debugging in ADT (ABAP Development Tool) on Eclipse 2022-12 [message #1857736 is a reply to message #1857733]

Thu, 23 February 2023 06:22

Eclipse User

Hi Ed,

ADT (ABAP Developemrn Tool) Plugins are developed by SAP and they release new version of it quarterly . I have been using these Plugins with Eclipse for at least 4 years now but never had this issue before .

I am check in SAP forums parallely . But not sure if it has anything to do with Eclipse/JRE upgrade either . Hence checking here as well.

Re: Problem with Debugging in ADT (ABAP Development Tool) on Eclipse 2022-12 [message #1857739 is a reply to message #1857736]

Thu, 23 February 2023 08:03

Eclipse User

Now that I think about it, it sounds like this question:

https://www.eclipse.org/forums/index.php/mv/msg/1112563/1857710/#msg_1857710

Looking in the Error Log view is good for finding such clues about what's going wrong...

Re: Problem with Debugging in ADT (ABAP Development Tool) on Eclipse 2022-12 [message #1857808 is a reply to message #1857739]

Mon, 27 February 2023 03:40

Eclipse User

Below is what's showing in the error log , but no sure what to make of it :

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)

Attachment: Error Log Eclipse Debuggign Issue.png
(Size: 152.23KB, Downloaded 226 times)

[Updated on: Mon, 27 February 2023 03:42] by Moderator

Re: Problem with Debugging in ADT (ABAP Development Tool) on Eclipse 2022-12 [message #1857810 is a reply to message #1857808]

Mon, 27 February 2023 04:44

Eclipse User

You really must ask SAP about the code they provide.

Previous Topic:	Problem with WindowBuilder & 125% scaling Windows 10
Next Topic:	Errors trying to integrate existing Dynamic Web Project

Goto Forum:

-=] Back to Top [=-

Current Time: Thu May 15 15:55:22 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter