Splint does a good job tracking down memory leaks in C code. Every malloc() should have a matching free(). But BoehmGC-collected code uses GC_MALLOC() with no matching GC_FREE(). This makes Splint go
I have the following code static pthread_mutex_t watchdogMutex = PTHREAD_MUTEX_INITIALIZER; static pthread_cond_t watchdogCond = PTHREAD_COND_INITIALIZER;
I\'m trying to chec开发者_JAVA技巧k a C program with Splint (in strict mode). I annotated the source code with semantic comments to help Splint understand my program. Everything was fine, but I just c
This is my first time using splint (from Ubuntu repositories) and I immediately got hit by a WTF. The error message:
Closed. This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this
I\'m trying to run splint on a C source that includes complex.h from the standard C library to support complex arithmetic.
I want to run splints whole program analysis on my system. However t开发者_JS百科he system is quite large and different parts are compiled with different compiler defines and include paths. I can see
I have been trying out Splint with a C program I recently wrote and trying to understand and remove the warnings it gives. One I understand but can\'t understand how to remove it comes from the follow
I compiled ( no warnings ) the hello-5.c example from \"The Linux Kernel Module Programming Guide\" and when I tried to insmod it, I received the following error: