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

Fix uninitialized variables #707

Open
mmaherwelsh opened this issue Apr 30, 2015 · 2 comments
Open

Fix uninitialized variables #707

mmaherwelsh opened this issue Apr 30, 2015 · 2 comments

Comments

@mmaherwelsh
Copy link
Contributor

MANY MANY of our modules have uninitialized variables which crash our code every once in a while. We need someone to look through the modules and check that all our variables are correctly initialized, even if the code isn't currently crashing.

@chachi
Copy link
Contributor

chachi commented Apr 30, 2015

If you can run valgrind on the robot/run the code under valgrind on desktop Linux, that might save you lots of headaches of combing through the code for uninitialized variables. Plus, you'll get all your memory leaks!

@egoogins
Copy link
Member

egoogins commented May 1, 2015

Static analysis tools are also pretty helpful / easy to use if somebody
wants to try using cppcheck: http://cppcheck.sourceforge.net/

On Thu, Apr 30, 2015 at 6:05 PM Megan Maher [email protected]
wrote:

Perfect, thanks! We'll get someone on it. Fixing memory leaks will also be
very useful.


Reply to this email directly or view it on GitHub
#707 (comment)
.

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

5 participants