Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve code with splint #32

Open
Lokaltog opened this issue Mar 6, 2014 · 2 comments
Open

Improve code with splint #32

Lokaltog opened this issue Mar 6, 2014 · 2 comments

Comments

@Lokaltog
Copy link
Owner

Lokaltog commented Mar 6, 2014

Tried running some of our source code through splint, and it spews out a ton of warnings. Some of these warnings should probably be looked into (buffer overflow issues, possible null pointers, etc). Here's a command that can be run from the project root:

splint [file.c] -I. -I `pkg-config --cflags gtk+-3.0 webkitgtk-3.0`

Output for src/wkline.c
Output for src/wkline/widgets.c

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@nHurD
Copy link
Contributor

nHurD commented Mar 11, 2014

Valgrind is another useful tool for checking memory leaks and the like. It also may be a bit disheartening to run at times...

@Lokaltog
Copy link
Owner Author

Yep, I've tried to use it a couple of times on wkline. It's pretty annoying to run with webkit, it spits out a ton of warnings and most of them stem from somewhere in the webkit engine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants