Thanks Alex,
I was able to write a variable analyzer using the compile_database.
https://gist.github.com/thesamprice/d4a19102aa4fe11fb96a75df57b9fcfe
On Mon, May 15, 2023 at 9:31 PM Sam Price wrote:
>
> Thanks Alex,
> I was able to run cppcheck.
> I had to install the newest cppcheck from source
Results from cppcheck
cpukit/include/sys/timetc.h:17:0: error: #error "no user-serviceable
parts inside" [preprocessorErrorDirective]
#error "no user-serviceable parts inside"
^
testsuites/samples/capture/test1.c:97:5: error: Uninitialized
variable: i [uninitvar]
i++;
^
cpukit/libblock/src
Thanks Alex,
I was able to run cppcheck.
I had to install the newest cppcheck from source to get access to the
--project flag.
i ran
bear ./waf
and then
cppcheck --project=compile_commands.json
It returned a few static analysis errors if interested.
I'll attach the results when it finishes running
Not sure if this helps but here is the script used to run Coverity
https://github.com/joelsherrill/rtems-cron-helpers/blob/main/rtems-run-coverity
On Mon, May 15, 2023, 10:03 AM Alex White wrote:
> You should be able to use `bear` (https://github.com/rizsotto/Bear). I
> have it installed via my
You should be able to use `bear` (https://github.com/rizsotto/Bear). I have it
installed via my package manager.
After a `./waf clean`, run `bear -- ./waf` to generate compile_commands.json.
Then you should be able to run `cppcheck --project=compile_commands.json`.
Alex
On Mon, Jun 13, 2022, 8:38 PM Chris Johns wrote:
> On 10/6/2022 12:09 am, Joel Sherrill wrote:
> > With Matthew addressing new warnings from GCC 12,
>
> I have posted some warning fixes for the arm and aarch64. They let those
> archs
> build warning free without the testsuite. I hope it helps.
>
On 10/6/2022 12:09 am, Joel Sherrill wrote:
> With Matthew addressing new warnings from GCC 12,
I have posted some warning fixes for the arm and aarch64. They let those archs
build warning free without the testsuite. I hope it helps.
Chris
___
devel mai
On 03/27/2015 09:33 AM, abd el-hamed Amer wrote:
Dear All,
First i thank Dr. joel for his advice in my last e-mail about this
project. I already submitted a proposal. So please review it and I
would be happy to hear your comments.
I repeated my comments from the mailing list and added more.
On 03/26/2015 04:23 AM, abd el-hamed Amer wrote:
Dear Dr. Joel sherrill & All,
I have chosen static analysis of stack usage for RTEMS, and I working
now on my proposal. can you advice me about the latest work on this
topic and which parts see it's important to focus in?
This is an idea that
