mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-04-29 19:45:01 +02:00
Bug 408522. Filter out project_classpath variable since it may sometimes
have a very large value exceeding shell limit. Change-Id: If67ca6a9b82f9c8de7d514fa236ab1a781f000d7 Reviewed-on: https://git.eclipse.org/r/13147 Reviewed-by: Marc Khouzam <marc.khouzam@ericsson.com> Reviewed-by: Sergey Prigogin <eclipse.sprigogin@gmail.com> IP-Clean: Sergey Prigogin <eclipse.sprigogin@gmail.com> Tested-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
This commit is contained in:
parent
0709b4314d
commit
a847e62681
1 changed files with 5 additions and 1 deletions
|
@ -440,7 +440,11 @@ public class LaunchUtils {
|
|||
ICdtVariable[] build_vars = CCorePlugin.getDefault().getCdtVariableManager().getVariables(cfg);
|
||||
for (ICdtVariable var : build_vars) {
|
||||
try {
|
||||
envMap.put(var.getName(), var.getStringValue());
|
||||
// The project_classpath variable contributed by JDT is useless for running C/C++
|
||||
// binaries, but it can be lethal if it has a very large value that exceeds shell
|
||||
// limit. See http://bugs.eclipse.org/bugs/show_bug.cgi?id=408522
|
||||
if (!"project_classpath".equals(var.getName())) //$NON-NLS-1$
|
||||
envMap.put(var.getName(), var.getStringValue());
|
||||
} catch (CdtVariableException e) {
|
||||
// Some Eclipse dynamic variables can't be resolved dynamically... we don't care.
|
||||
}
|
||||
|
|
Loading…
Add table
Reference in a new issue