Fortify on Visual Studio 2010 C++ project - error MSB6006: -1073741701 - c++

I am trying to run fortify on a VS2010 C++ project. I created a very simple hello world project and tried to run fortify with the following command:
sourceanalyzer.exe -b sample devenv sample.sln /REBUILD
I keep getting this error:
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\Microsoft.Cpp.Win32.Targets(147,5): error MSB6006: "CL.exe" exited with code -1073741701.
the complete build log is:
Microsoft (R) Visual Studio Version 10.0.30319.1.
Copyright (C) Microsoft Corp. All rights reserved.
1>------ Rebuild All started: Project: sample, Configuration: Debug Win
32 ------
1>Build started 09/07/2012 12:13:33 PM.
1>_PrepareForClean:
1> Deleting file "Debug\sample.lastbuildstate".
1>InitializeBuildStatus:
1> Creating "Debug\sample.unsuccessfulbuild" because "AlwaysCreate" was specified.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\Microsoft.Cpp.Win32.Targets(147,5): error MSB6006: "CL.exe" exited with code -1073741701.
1>
1>Build FAILED.
1>
1>Time Elapsed 00:00:00.09
I did not get any additional errors. My OS is Windows7 64 bit. My project is a 32 bit console application. I am using fortify 32 bit with version: "Fortify Source Code Analyzer 5.9.5.0007"
I tried browsing microsoft pages for the error, but it is apparently a generic error code. I am suspecting an incompatibility, but am not able to narrow it down. Can you tell me where I am going wrong?
Update: Some more info:
With VS2010's cl.exe, it runs clearly. The error is thrown by Fortify's cl.exe. I checked the error code, and apparently, cl.exe is unable to start. I cross checked with dependency walker, and it is missing a couple of dlls(gpsvc.dll and IEShims.dll). I have a 64 bit Windows installation, but cl.exe is 32 bit and I do not have 32 bit versions of those DLLs. I am not sure if this is the root cause, because they are delay loaded and might not cause the error mentioned.

The problem was with the Fortify version. Downloading Fortify360 Version 3.2 resolved the issue.

Related

Unreal engine 4.26.2 source version errors when running

I'm trying to set up UE4.26.2 source version but haven't been successful. I have cloned the repo from github, ran Setup and GenerateProjectFiles without errors, set development editor and x64 in Visual studio 2019 and built it without errors but when I try to run the UE I always get the same two errors:
Build started...
1>------ Build started: Project: UE4, Configuration: Development_Editor x64 ------
1>Building UE4Editor and ShaderCompileWorker...
1>Using Visual Studio 2019 14.34.31937 toolchain (C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933) and Windows 10.0.20348.0 SDK (C:\Program Files (x86)\Windows Kits\10).
1>Building 2 actions with 16 processes...
1> [1/2] UE4Editor.exe
1>LINK : fatal error LNK1104: cannot open file 'D:\UE4.26.2\UnrealEngine-4.26.2-release\Engine\Binaries\Win64\UE4Editor.exe'
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.MakeFile.Targets(45,5): error MSB3073: The command "..\..\Build\BatchFiles\Build.bat -Target="UE4Editor Win64 Development" -Target="ShaderCompileWorker Win64 Development -Quiet" -WaitMutex -FromMsBuild" exited with code 6.
1>Done building project "UE4.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 2 up-to-date, 0 skipped ==========
LNK1104 cannot open file 'D:\UE4.26.2\UnrealEngine-4.26.2-release\Engine\Binaries\Win64\UE4Editor.exe'
MSB3073 The command "....\Build\BatchFiles\Build.bat -Target="UE4Editor Win64 Development" -Target="ShaderCompileWorker Win64 Development -Quiet" -WaitMutex -FromMsBuild" exited with code 6.
I have tried various different combinations of VS components, I have installed .net Desktop dev, desktop dev with c++ and game dev with c++. I am using .NET Framework 4.8 SDK with all the previous 4.x targeting packs. I have tried deleting certain content from the Win64 folder and other files which I can't recall, but after I run the UE4 it always builds them again so the errors persist.
I solved the issue. My avast antivirus put the "UE4Editor.exe" into quarantine, then I restored it and compiled and voila, it works

Cannot build console application with Microsoft Visual Studio 2019

I just installed the community version of VS 2019. I selected to build a console application that it created for me ("hello world" program). The file created is called ConsoleApplication1.cpp. I went to the build menu, selected build, and get the following error:
1>------ Build started: Project: ConsoleApplication1, Configuration: Debug Win32 ------
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppBuild.targets(441,5): warning MSB8003: The WindowsSDKDir property is not defined. Some build tools may not be found.
1>ConsoleApplication1.cpp
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.24.28314\include\yvals.h(12,10): fatal error C1083: Cannot open include file: 'crtdbg.h': No such file or directory
1>Done building project "ConsoleApplication1.vcxproj" -- FAILED.
I tried to follow directions listed elsewhere on stackexchange. When I select "Project -> Properties" the Windows SDK field is blank. A value I typed in from the other StackExchange message creates an error that that version of the SDK cannot be found. So I deleted the version of the SDK and made it blank again. I also tried using "10.0" Here is where I received the advice:
Visual Studio 2017 errors on standard headers
Perhaps I did not install all the needed components. I recently checked off: "Windows Universal CRT SDK" (as per the instructions), but the build still fails. The warning is interesting. I looked that up also but have not found a solution that works. My "Platform Toolset" is Visual Studio 2019 (v142).
What might still be missing to build a console application? Thank you. I am working on Windows 7.

Error building libarchive for c++ Visual Studio 2010 Professional

I am trying to build libarchive for c++ Visual Studio 2010 Professional. Everything seems to be fine, the tests run OK, up until I get the following error:
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(151,5): error MSB6006: "cmd.exe" exited with code -1073741571.
Build FAILED.
I have googled and searched for this exact error on SO but cannot find anything.
Thank you.

Marmalade ErrorCode 4 while building mkb project

I've got a project from my teacher, that I should run in the Marmalade Hub. I've imported this project en tried to run it. At first I got an error with the error code 7.
error: Visual Studio 2013 Express Windows Desktop requested but not found instal
led.
FAILED (error code=7)
I've fixed this problem to change the C++ Development (IDE's and Compilers) from 'Visual studio Express 2013 Windows Desktop' to 'Visual Studio 2013' (see image below). I did this change, because I do have 'Visual Studio Proffesional 2013 for Windows Desktop' and not 'Visual Studio Express 2013 for Windows Desktop'. 'Visual Studio 2013 Proffesional 2013 for Windows Desktop' doesn't exist in the drop down.
I tried again to run the project (see image below) and I did get another error with the error code 4:
-- Visual Studio Output --
1>------ Build started: Project: minimal_marmalade_vc12, Configuration: x86 Debu
g Win32 ------
1>LINK : warning LNK4075: ignoring '/INCREMENTAL' due to '/FORCE' specification
1>LINK : fatal error LNK1181: cannot open input file 'cgl_d.lib'
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
-- End Visual Studio Output --
error: build failed: '['C:\\Program Files (x86)\\Microsoft Visual Studio 12.0\\C
ommon7\\IDE\\devenv.exe', 'minimal_marmalade_vc12.sln', '/build', 'X86 Debug', '
/out', 'vs_output_11728.log']' (1)
FAILED (error code=4)
I hope you guys (or girls ;) ) can solve this problem. Thanks!
Maybe that your project uses the library Core Media Library. Check whether used somewhere in the code header file cgl.h If so, then reinstall Core Media Library Instalation instructions you find in this guide

CUDA + Visual Studio = suppressed output window

Normally, when I use Visual Studio to do a build, I see warnings and errors shown in the output pane, e.g.
1>------ Build started: Project: pdcuda, Configuration: Release x64 ------
Compiling...
foo.cpp
Linking...
foo.obj : error LNK2001: unresolved external symbol "foo"
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
I'm doing some GPU programming with CUDA. Upon upgrading to 2.1, I no longer get any useful output in Visual Studio. For example, all I now see is:
1>------ Build started: Project: pdcuda, Configuration: Release x64 ------
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
The other details can be found in BuildLog.htm, but it's inconvenient to hunt that file down all the time.
Does anyone know how to force Visual Studio to show the output in its output pane?
Things that don't help:
uninstalling CUDA: the problem persists in all projects
Tools > Options > Projects and Solutions > Build and Run > MSBuild project build output verbosity: changing this pulldown, even to "Diagnostic" has no discernable effect.
EDIT: Additional things that don't help:
devenv.exe /resetsettings
devenv.exe /resetuserdata
UPDATE (in response to Die in Sente): It's now working on one of the two machines (I'm not sure what I did to fix it though). The machine that's still having problems has a CUDA Visual Studio Wizard installed that has caused similar problems before. The still-broken machine had version 15.00.21022.8 of the compiler. The working machine has 15.00.30729.1. After making a backup, I transferred "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\amd64" from the working to the broken machine. I observe no changes in behavior on the broken machine.
I have exactly the same problem, but without CUDA. Today Visual Studio just decided it wasn't going to show any build messages anymore. It was working fine, then one of my builds it just stopped working. The problem persists over all my projects now, and persists over reboots. I also see the correct messages in buildlog.htm. This is ridonkulous!
EDIT: Ooh, I used the add/remove programs to do a repair, and now it works again! Yeah!
did you tried to reset IDE
devenv.exe /resetsettings
or
devenv.exe /resetuserdata
I also recently install CUDA 2.1 (on top of 2.0 I believe). The default installation for CUDA 2.1 moved the SDK from
C:\Program Files\NVIDIA Corporation\NVIDIA CUDA SDK\
to
C:\Documents and Settings\All Users\Application Data\NVIDIA Corportation\NVIDIA CUDA SDK\
which initially caused me some problems. Are all of your paths resolving correctly?
This might sound like a far out suggestion. Get the CUDA SDK and try your code with the sample CUDA-C++ project in there. Maybe something changed in the build rules for CUDA v2.1.
If you go to Tools->Options->Projects and Solutions->Build and Run. Last property is "MSBuild Project build output verbosity". It defaults to Minimal, change it to normal and the build messages will show up in Output window.
This also enables any <Message Text="test message"></Message> output to show up in Visual Studio Build Output Window.
Final solution: reinstall the OS.