Every time we have a new build, it goes into a different build root folder with (usually) the same subfolders. Is there a way to create a project baseline from an initial folder and then subsequently see what changed by pointing to the next newer folder? I've been creating new projects for new builds, but I was hoping I create a build based upon the previous one with some form of version control or the ability to see diff changes. Thanks, Bassam
I'm getting an error for the following line of code. The if statement forces it to be a positive shift value. Sadly, it's not my code. if (bit_count < 0) { /*+ shift out the extra bits */ * ((UNSIGNED_32 *) extract_value_ptr) >>= (0 - bit_count); }
Not to hijack this discussion, but the GUI crashes for me as soon as I open a project. I started a new one several times and the GUI is fine for editing. When I click analyze, it crashes. When I reopen it and attempt to reopen the project, it crashes. If I don't reopen the project and select edit instead, it opens the file for editing and I can make and save modifications. However, if I click open or analyze, it crashes every single time. Deleting everything and starting new does nothing. I have...
Not to circumvent this discussion, but the GUI crashes for me as soon as I open a project. I started a new one several times and the GUI is fine for editing. When I click analyze, it crashes. When I reopen it and attempt to reopen the project, it crashes. If I don't reopen the project and select edit instead, it opens the file for editing and I can make and save modifications. However, if I click open or analyze, it crashes every single time. Deleting everything and starting new does nothing. I have...
Is this comment still valid in the MISRA code? Total number of rules: 143 I'm counting a higher number.
If there's goodies in there, go for it.
Change the Misra path to not have spaces in it. It doesn't work with spaces.
It failed from the command line as well. What I did notice is that for the file that I'm interested in, the dump file created just for that file in its own project was way smaller (22219 lines) than the dump file created just for that file when included with the entire project (560963 lines). Yet somehow, the smaller dump file is capturing the necessary info. Unfortunately, I cannot share the code or the dump files. Commands used: For the Project cppcheck --dump *.c (fails to capture anything for...