cppcheck

Hi Daniel, I downloaded and installed it and it works perfect. This is great news, because the problems with installing the 1.70 version caused me to skip 1.71. Now I'm happy again :-)

Hi Daniel, the download links on the site http://cppcheck.sourceforge.net/ seem to be very strange: ftp://cppcheck.osuosl.org/cppcheck/1.72/cppcheck-1.72-x64-Setup.msi and ftp://cppcheck.osuosl.org/cppcheck/1.72/cppcheck-1.72-x86-Setup.msi Could you please check this?!

Cppcheck-1.72 has been released. General changes: - Added platform files to customize characteristics of different target platforms - Added setting to configure the default sign of integral variables and bit size of type 'char' - Added option -E ... [More] (only preprocess the code) - Option --dump now outputs data for each configurations, not only the last one - Several qmake project files have been removed Removed checks: - Check for unnecessary forward declaration has been removed New checks: - Warn about shifting negative values - Detect statements with undefined execution order (pre-C++11 code) - Added a generic check to discourage usage of specific functions, replacing CheckNonReentrantFunctions and CheckObsoleteFunctions Checking improvements: - Several improvmenets to ValueFlow analysis - Improved ValueType handling, refactored several checks to make use of it - Improved memory leak checking - Improved Container specification in Library files, rewrote some checks based on it - Improved handling of character literals - Improved checking for non-interlocked accesses - Properly support <cstdint> types in namespace std - Added some validation mechamisms to avoid crashs GUI: - Improved Library editor - Support "Enter" key in results tree - Properly detect editors on 64-Bit Windows - Added Japanese translation - Allow opening project file without extra parameter from command line Additionally, lots of false positives and bugs have been fixed and several existing checks have been improved. [Less]

For others, this appears to be the open ticket for this issue: http://trac.cppcheck.net/ticket/6980

I have managed to repair VS2015 by using msiinv to get a list of all msi install, then using msiexec -x {product code} on everything that was associated with VS2015... then reinstalling. I think what happened was: 1) cppcheck copied the wrong DLLs. ... [More] 2) Visual studio then collapsed on startup 3) I tried to repair VS, but I suspect that the repair process also depended on the damaged dlls, so this made matters worse. 4) I followed the advice above to remove the damaged dlls, but by now the VS installation was in a heap and normal installations were never going to work. Anyhow, thank you for your input. Perhaps more checking should be done on new releases of cppcheck? [Less]

I don't know what type of error you are getting. Could you share your error code for the install?

Well I tried all that and this does not appear to be the problem. It is very difficult to find the correct time for the failure. Some logs only give the time to an accuracy of 1 second, which is hopeless. The system Event viewer gives different times ... [More] for the MSI installer fail to the logs, and the logs only give time to the nearest ms. There is no SysWOW64 error anywhere near any of these times. Looking through the ProcessMonitor there is no obvious failure point. There are repeated patterns (these look like walking through registry directory trees) that go on for many hundres of lines, and these do include horrible-looking errors (BUFFER_OVERRUN etc) but these do not seem to be fatal AFAICT). [Less]

I don't think that it would be a 32 bit DLL in the 64 bit directory, since Visual Studio is a 32 bit application. I don't know what kind of error you are getting when reinstalling Visual Studio. But I got the fatal error when installing the "Team ... [More] Explorer" component. I found a link on StackOverflow where a russian guy described how he was able to track down his problem using ProcessMonitor. I followed the same procedure and was able to find the offending DLL file that was preventing my install. Start with downloading ProcessMonitor: https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx The process is as follows: 1. Uninstall Visual Studio 2. Start ProcessMonitor and start to capture logs. 3. Start the Visual Studio installation. 4. When the installation breaks down, stop the ProcessMonitor logging. 5. Look in your %TEMP% folder for the installation logs. You will find the point in time where the installation fails. 6. Go to that location in time in your ProcessMontor logs. 7. You will see that the VSIX installer tries to load diffrent DLL files. The pattern here is that it tries to find the file and then load it. If it can't find a DLL file the ProcessMonitor result will be NAME_NOT_FOUND. If it finds the file the result will be SUCCESS and the search for that DLL will terminate. But here is the key to finding the error (at least in my case): If it finds a file that it cannot use, the the result will still be SUCCESS, but since it cannot use it (due to being for the wrong architecture) the installer will try to find the file at a different location. It will look like this in the ProcessMonitor logs: Hopefully you will be able to find the offending DLL file the same way. Then it is just a matter of uninstalling the redistributables, deleting this file and reinstalling the redistributables again. Here is a link to the StackOverflow thread that got me going in the right direction: http://stackoverflow.com/questions/33855177/multiple-errors-installing-visual-studio-2015-community-edition/33881460#33881460 [Less]

Thank you for the information. Sadly, this does not fix the error. I still cannot get Visual Studio 2015 repaired after 3 weeks. If you know which files the 1.71 x64 cppcheck updated the system with, this would be MOST useful to know, so I can ... [More] attempt to clean up the mess. If you are saying that the x86 cppcheck installation updated the sysWOW64 folder (which should hold x86 dlls) with an x64 dll, then is it possible that the reverse happens when installing the x64 dlls? I am clutching at straws here... [Less]

See above post how to fix this error.