eclipse 11.3 eclipse-cpp-2023-09-R-linux-gtk-x86_64 has issues with cdtdebug

[anon99]

Describe the bug
Install 2023-09-R [2023-06-R works fine]
Install/setup cdtdebug
https://github.com/eclipse-cdt/cdt/blob/main/StandaloneDebugger.md
Start cdtdebug
~/cdtdebugger/cdtdebug.sh
Get a whole load of errors in logfile:-

!ENTRY org.eclipse.cdt.debug.application 4 0 2023-10-10 14:30:15.839
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.cdt.debug.application [35]
Unresolved requirement: Import-Package: org.eclipse.debug.ui.actions
-> Export-Package: org.eclipse.debug.ui.actions; bundle-symbolic-name="org.eclipse.debug.ui"; bundle-version="3.18.100.v20230802-1257"; version="0.0.0"
org.eclipse.debug.ui [75]
Unresolved requirement: Require-Bundle: org.eclipse.ui.ide; bundle-version="[3.5.0,4.0.0)"
-> Bundle-SymbolicName: org.eclipse.ui.ide; bundle-version="3.21.100.v20230825-1346"; singleton:="true"

Expected behavior
Pop up a dialog requesting cdtdebug information

I concluded the installation must have internal versioning discrepancies so I deleted the whole tree and installed
eclipse-cpp-2023-06-R-linux-gtk-x86_64.tar.gz
Which works as expected.

[anon99]

Did you build a tar-kit and check that? if not point me at it and I'll give it a try.

[jonahgraham]

Did you build a tar-kit and check that? if not point me at it and I'll give it a try.

That is wonderful!

The build is running now on https://ci.eclipse.org/simrel/ and that triggers the build on https://ci.eclipse.org/packaging/ which will eventually publish its results https://download.eclipse.org/technology/epp/staging/. That whole process is expected to take probably another 6 hours.

Tomorrow we build the M3 build of the 2023-12 release (with RC1 and RC2 following in the next couple of weeks). That will be available https://www.eclipse.org/downloads/packages/release/2023-12/m3 on Friday morning at 10am (Ottawa time).

If you can test M3 that would be great.

However I am not very optimistic - all the great work that has been happening to resolve all the old third-party libraries in Eclipse ecosystem has led to some instability for the standalone debugger which is built in an "unusual" way. While I think my fix has a chance of resolving this, I am unsure. I will reopen until we get this checked through the whole flow.

[jonahgraham]

2023-12 M3 still does not work. Unfortunately there are a bunch of problems in M3 related to versions of libraries causing issues and we'll try to get this fixed for RC1 now.

[jonahgraham]

Full log of failure: 1700188701843.log