Jonah Graham 2980b60439 Include system environment when debugging core build ... When doing a local launch, the only environment passed to the debuggee was the modified variables, typically just PATH. This meant all the other environment was lost. This change does the same thing as all the other calls to setBuildEnvironment and passes in the initial system environment. I added a small note to the API of setBuildEnvironment to try to avoid this error in the future.		2025-02-25 22:02:06 -05:00
..
org.eclipse.cdt.dsf.gdb	Include system environment when debugging core build	2025-02-25 22:02:06 -05:00
org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui	Update to latest versions of build tools (#986)	2025-01-06 20:37:10 -05:00
org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui.tests	Upgrade build.properties warnings to errors	2022-11-06 18:29:28 -05:00
org.eclipse.cdt.dsf.gdb.tests	Upgrade build.properties warnings to errors	2022-11-06 18:29:28 -05:00
org.eclipse.cdt.dsf.gdb.ui	Common tab for Core Build local launch configuration. (#970)	2024-12-15 16:26:10 -05:00
org.eclipse.cdt.examples.dsf.gdb	Upgrade build.properties warnings to errors	2022-11-06 18:29:28 -05:00
org.eclipse.cdt.gnu.dsf-feature	Bump version to CDT 12.0.0 (#911)	2024-10-08 12:52:15 -04:00
org.eclipse.cdt.gnu.multicorevisualizer-feature	Bump version to CDT 12.0.0 (#911)	2024-10-08 12:52:15 -04:00
org.eclipse.cdt.tests.dsf.gdb	Add some extra info when terminate fails in tests	2025-01-24 14:04:47 -05:00
pom.xml	Bump version to CDT 12.0.0 (#911)	2024-10-08 12:52:15 -04:00