Jump to content

  • Log In with Google      Sign In   
  • Create Account


VC++ F5 and Ctrl+F5, I'm mad...


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
21 replies to this topic

#21 brx   Members   -  Reputation: 708

Like
0Likes
Like

Posted 30 August 2012 - 10:39 AM

I normally use valgrind to check for things like this. It walks through your program and gives dynamic warnings on uninitialized variables and also memory leaks

Vagrind would have been an option, but he stated he's using the Visual Studio and afaik valgrind does unfortunately not work in windows.

However, I just remembered that starting with VS2012 the static code analysis is included in all versions starting with professional (it used to be limited to higher versions before). That should have caught it as well. Additionally, they finally made the profiler and the concurrency visualizer available for VS professional as well.

Sponsor:

#22 Hodgman   Moderators   -  Reputation: 29497

Like
0Likes
Like

Posted 30 August 2012 - 10:42 PM

Good static analysys tools should be good for this -- there's an article on the site that talks about catching buggy memset calls that were supposed to initialize allocations but didn't.




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS