Error: spawn E2BIG during Updating the CppTools IntelliSense Configuration Provider.

[alanpawlak]

This issue became present when plugin got autimatically updated to version 0.10.26. Same problem on 0.11.4 (pre-release)

Using my specific configuration and build target and Makefile: Clean Configure.

This is a large commercial project, so I cannot provide specific details. Setup involves multiple setup scripts and makefiles.

Version 0.10.26.

Error: spawn E2BIG
Exception thrown during the configure process: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received an instance of Error
Configure elapsed time: 49.232

Version 0.9.10 (working fine)

Parsing build targets elapsed time: 0.005
Configure finished. The status for all the subphases that ran:
loadFromCache: return code = 0, elapsed time = 0.734
generateParseContent: return code = 2, elapsed time = 21.506
preprocessParseContent: return code = 0, elapsed time = 0
parseIntelliSense: return code = 0, elapsed time = 25.896
parseLaunch: return code = 0, elapsed time = 0.69
dryrunTargets: return code = 2, elapsed time = 1.014
parseTargets: return code = 0, elapsed time = 0.005
Configure succeeded.
Configure elapsed time: 69.531

[gcampbell-msft]

@alanpawlak Could you install a specific version, 0.10.16, and test if it's working in that version?

However, either way, it may be difficult to investigate and implement a fix for without a reproduction project. Thanks.

[alanpawlak]

Just tried 0.10.16 and it works correctly. Next I tried 0.10.17 and I got the same error as above. I can try to provide some logs, as soon as they do not disclose any confidential information.

[gcampbell-msft]

@alanpawlak Could you try this vsix? makefile-tools.zip

You'll need to modify the file extension from .zip to .vsix and then install it manually through the extensions UI in VS Code.

[alanpawlak]

Configure finished. The status for all the subphases that ran:
loadFromCache: return code = 0, elapsed time = 0.779
generateParseContent: return code = 2, elapsed time = 21.374
preprocessParseContent: return code = 0, elapsed time = 0
parseIntelliSense: return code = 0, elapsed time = 24.026
parseLaunch: return code = 0, elapsed time = 0.689
dryrunTargets: return code = 2, elapsed time = 0.794
parseTargets: return code = 0, elapsed time = 0.005
Configure succeeded.
Configure elapsed time: 47.761

This appears to have worked sucessfully. To confirm it lists version as 0.7.0.

[gcampbell-msft]

@alanpawlak What operating system are you on? Thanks

[alanpawlak]

Linux Mint Debian Edition working within docker container

[gcampbell-msft]

On the most recent version of the extension, could you set makefile.loggingLevel to Debug and reproduce the issue and send that? Or as much as you can without sending compromising information?

[gcampbell-msft]

@alanpawlak Either way, I merged the change sent in the vsix that you tested into main just now, the fix will get released on the pre-release channel tomorrow 👍

[alanpawlak]

Found compiler command: x86_64-XXX-linux-g++  -m64 -march=corei7 -mtune=corei7 -mfpmath=sse -msse4.2 --sysroot=PATH

[Very long list of all object files (.o) separated by space ]
[List of compiler flags]
[-o output native executable]

Error: spawn E2BIG
Exception thrown during the configure process: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received an instance of Error
Configure elapsed time: 61.462
Sending telemetry: eventName = configure
properties: firstTime = "false",makeDryRun = "true",readCache = "true",isClean = "true",processTargetsSeparately = "true",resetBuildTarget = "false",triggeredBy = "command pallette (clean configure)",buildTarget = "..."
measures: numberBuildTargets = "[REMOVED]",numberLaunchTargets = "[REMOVED]",numberIndexedSourceFiles = "[REMOVED]",numberMakefileConfigurations = "[REMOVED]",totalElapsedTime = "61.462",exitCode = "-5"

This is all i can provide, this is the excerpt from where the error occurs.

[gcampbell-msft]

@alanpawlak Got it. Thanks for the information. This issue should be fixed as of tomorrow in pre-release version 0.11.5. Thanks.