Menu

Interesting Bug

2018-10-30
2018-11-12
  • Bassam Abdul-Baki

    Created a CPPCheck project on our network, but the MISRA analysis aren't appearing at work.
    Decided to create a test one on my local drive. I did this by clicking on File | New without closing the previous one. Not sure if it is relevant. (Note: I got MISRA working at home. The only difference is I can't install CPPCheck at work.)
    Gave the local CPPCheck project the exact name as the network one and placed it in the same location as my local test source code. Dummy test project so I'm being lazy.
    Ran the analysis and the new project was picking up files from the previous one. Maybe File | New Project does not do a close project first?
    Checked the directory path. Closed the project. Opened it. Still picking up the previous network paths in addition to the new local paths.
    Clicked on Analyze | Directory. It prompted me with a warning saying I have to close the project.
    Closed the project yet again.
    Clicked on Analyze | Directory and selected the local project folder.
    It told me that it found a CPPCheck project and if I want to load that instead.
    Yes, please!
    Eureka! It loaded only the local paths, but still no MISRA analysis. I assume that until the project is reanalyzed, the previous paths were saved with the new paths.

    My other issue is, does the MISRA analysis not work unless CPPCheck is installed?
    I had to copy the files from home since I cannot install it at work. Both OSes are 64-bit. Windows 7 vs. Windows 10 though.

     
  • Bassam Abdul-Baki

    I can't seem to get the MISRA to work at work since I was not able to install CPPCheck.

    Looking at Dependency Walker, I appear to be missing the following DLLs:

    API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
    API-MS-WIN-CORE-WINRT-L1-1-0.DLL
    API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
    API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
    DCOMP.DLL
    IESHIMS.DLL

     
  • versat

    versat - 2018-11-12

    Here https://sourceforge.net/p/cppcheck/discussion/general/thread/96a2477c7c/ you wrote that it is working now at work. Was the redistributable package the problem? Is this issue resolved then?

     
    • Bassam Abdul-Baki

      This initial issue had nothing to do with Cppcheck running, although the MISRA issue is also mentioned.

      The issue here is that when I created different projects through the GUI, the files from the previous project that were displayed in the GUI were still being displayed in the new project. It took some testing, but I think I had to clear the results manually or scan the entire directory before the other project's results were permanently cleared.

      Opening different projects to analyze did not clear the previous project's data for some reason and files from different projects were overlapping. That's why I thought it was a bug, since it happened several times.

      I did figure out that clearing the W7-cppcheck-build-dir folder manually fixed all that.

      As for my MISRA comment, I noticed that at work while trying to clear the project files. I then created a separate discussion since my MISRA issue (at work) is still not resolved.

      My home and work computers had the same file display issue. However, only my work computer has the MISRA issue. That's why this thread was convoluted. I've been working on Cppcheck both at home and at work.

       

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.