Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
ArthurVa_IBM Absent Member.
Absent Member.
1683 views

Compiling with instrumentation "Error detection with coverage" causes error messages.

An error window titled"cl.exe - Application error" pops up, with the message:

"The exception unknown software exception (0xc0000417) occured in the application at location 0x02545100.

Click on OK to terminate[...] CANCEL to debug [...]"

 Project compiles fine without instrumentation or with other instrumentation options.

 

Im on the devpartner trial version , 11.3.0. Windows 7 x64, and visual studio 2013.

Tags (1)
0 Likes
7 Replies
mlevis Absent Member.
Absent Member.

RE: Compiling with instrumentation "Error detection with coverage" causes error messages.

In the output window where the error shows up can you click on that and go to the code? If so can you copy & past that function in here pointing to the line that produces an error. Also can you past the full version of devpartner you have. This can be obtained from the Visual Studio about box.
0 Likes
ArthurVa_IBM Absent Member.
Absent Member.

RE: Compiling with instrumentation "Error detection with coverage" causes error messages.

Hi,
DevPartner version is: 11.3.1812.0 .
The error presented is:
>cl : Command line error D8040: error creating or communicating with child process

It does not point to any line of code.
This is the debug output of cl.exe if I choose to debug it:

'cl.exe' (Win32): Loaded 'C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\amd64_x86\cl.exe'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\ntdll.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\kernel32.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\KernelBase.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Program Files (x86)\MSBuild\12.0\Bin\amd64\FileTracker.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\advapi32.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\msvcrt.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\sechost.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\rpcrt4.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\msvcr120.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\ole32.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\gdi32.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\user32.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\lpk.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\usp10.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\amd64\mspdb120.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\version.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\imm32.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\msctf.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\cryptsp.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\rsaenh.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\cryptbase.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\amd64_x86\c1xx.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\msvcp120.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\amd64\mspdbcore.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Program Files (x86)\Common Files\Micro Focus\NMShared\CTI\11.1\X64\nmc2dll.dll'. Module was built without symbols.
'cl.exe' (Win32): Loaded 'C:\Program Files (x86)\Common Files\Micro Focus\NMShared\CTI\11.1\X64\nmcti.dll'. Cannot find or open the PDB file.
'cl.exe' (Win32): Loaded 'C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\amd64_x86\c2.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\shlwapi.dll'. Symbols loaded.
'cl.exe' (Win32): Loaded 'C:\Windows\System32\apphelp.dll'. Symbols loaded.
The thread 0x2b08 has exited with code 0 (0x0).
The thread 0x1980 has exited with code -1073740777 (0xc0000417).
The thread 0x1c24 has exited with code -1073740777 (0xc0000417).
The thread 0x20e8 has exited with code -1073740777 (0xc0000417).
The thread 0x27d8 has exited with code -1073740777 (0xc0000417).
The thread 0x134 has exited with code -1073740777 (0xc0000417).
The thread 0x2668 has exited with code -1073740777 (0xc0000417).
The thread 0xb0c has exited with code -1073740777 (0xc0000417).
The program '[7428] cl.exe' has exited with code -1073740777 (0xc0000417).
0 Likes
mlevis Absent Member.
Absent Member.

RE: Compiling with instrumentation "Error detection with coverage" causes error messages.

cl : Command line error D8040: error creating or communicating with child process

This error is usually produced when using multi process compilation and instrumentation is not launched that way. How is compilation being invoked? From the IDE or command line?
0 Likes
ArthurVa_IBM Absent Member.
Absent Member.

RE: Compiling with instrumentation "Error detection with coverage" causes error messages.

I'm compiling using the Visual Studio IDE (version 12.0.31101.00 update 4).
The project is indeed defined to use multi-process compilation- by disabling it in the project settings, the following error message showed up instead, with the same error code:

5>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(341,5): error MSB6006: "nmcl.exe" exited with code -1073740777.

This points to the following line:

<CL Condition="'%(ClCompile.PrecompiledHeader)' != 'Create' and '%(ClCompile.ExcludedFromBuild)'!='true' and '%(ClCompile.CompilerIteration)' == '' and @(ClCompile) != ''"
0 Likes
mlevis Absent Member.
Absent Member.

RE: Compiling with instrumentation "Error detection with coverage" causes error messages.

Either way with multi process or not should be working. Do you have the full path to which nmcl is being launched? I see you are using the native x64 versions of CL here. Also you are using an older trial version 11.3.1812 and the current that should be downloaded is 11.3.2163
0 Likes
ArthurVa_IBM Absent Member.
Absent Member.

RE: Compiling with instrumentation "Error detection with coverage" causes error messages.

Full path is C:\Program Files (x86)\Common Files\Micro Focus\NMShared\CTI\11.1\X64\nmcl.exe .
Running "C:\Program Files (x86)\Common Files\Micro Focus\NMShared\CTI\11.1\X64\nmcl.exe --version" produces:

"Micro Focus Compiler Driver v11.1.0.106
Copyright (c) Micro Focus 1997-2012. All rights reserved.

Error: can't locate Microsoft Visual C++;"

The tiral download link is expired so I am no longer able to download a newer version of devpartner.
0 Likes
mlevis Absent Member.
Absent Member.

RE: Compiling with instrumentation "Error detection with coverage" causes error messages.

I would suggest opening a ticket so we can send you the link to download the newer version and trouble shoot this further.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.