Actions from last meeting details
-
Action John/Torbjörn/Erik to try to resolve Bug
577263
-
Finalizing conversation on this
-
Concern about whether extra flags should be added to old project
-
See bug and related gerrit for any additional information
-
Still ongoing - so Action carried forward to next meeting again.
-
Action Jonah to see if he can make this intermittent failure fail reliably
to expose if this is the same race condition for Bug 577346 DONE
-
Action: Torbjörn to create bug for dark theme color issue in console. DONE
-
Action: Jonah to run the update to all license files in CDT with regards
to this gitlab issue IN PROGRESS
Minutes
-
Bug 579666: Improve dark theme on Windows and how to handle an API breaking change in Managed Build’s AbstractPage. See this gerrit
-
Action submit gerrit that
@Deprecated
for_removal should be added to fields
Done,
https://git.eclipse.org/r/c/cdt/org.eclipse.cdt/+/192718
-
Bug 579669 Test
regressions as a result of upgrade of Target Platform to latest version
-
Modules view purpose and removal
-
Modules view is supplied by Eclipse Platform
-
May be possible to hide it with Activities
I tried to do it with activities and yes, I can hide/remove the view from the entire Eclipse
IDE, but the view is still listed in the “Show Views” dialog and trying to opening it throws an exception and renders a broken view:
What I had in mind was a way to simply not show it by default in the “debug” perspective,
but still allow the user to open it manually if they wanted to.
-
Suspend enabled too early in Torbjörn’s launch sequence
-
Action (Erik) to send some info about enablements
-
For unmanaged projects is there a way to display the normally hidden settings?
What I was aiming for here is a way to save some generic data on the build configuration that
can be used by other views to, for example, identify the toolchain to be used.
A visual example is the prefix and path in the Cross GCC toolchain integration provided by CDT. The path and prefix could, for example, be used to automatically find the right GDB binary to launch during a debug session.
-
There is a bug in GDB 10 & GDB 11 that can cause GDB to quit unexpectedly and randomly
Problem also present in GDB 9 according to ’git tag --contains afe09f0b6311a4dd1a7e2dc6491550bb228734f8’!
-
See the (GDB bug 28711)[https://sourceware.org/bugzilla/show_bug.cgi?id=28711]
-
This may be able to be worked around in CDT by changing
org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl.NUMBER_CONCURRENT_COMMANDS to
1 to prevent there being multiple concurrent commands waiting in GDB input buffer.
I created
https://git.eclipse.org/r/c/cdt/org.eclipse.cdt/+/192719 for this issue, feel free to review/comment!
Will try to verify that it actually helps in the coming days.
Next Meeting
May 11
at 11am (Ottawa, Canada time)
