Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • 8
    Sadly, this is hella common in non-trivial C++ apps. If you're using source control, testing various changesets to narrow down what code change caused the issue can help, but maybe not feasible in this case. Commented Aug 8, 2014 at 2:54
  • Yeah, it really isnt feasable in my case. I basically went from working to completely and utterly broken for 2 month and then to the debugging stage where I have somewhat working code. The old system really didnt allow me to implement a my new kinda flexible network code without breaking everything. Commented Aug 8, 2014 at 3:02
  • 2
    At this point you may have to try and isolate each part. Take each class/subset of the solution, make a mock around it so that it can function, and test the living hell out of it until you find the section that fails. Commented Aug 8, 2014 at 3:10
  • start by commenting out portions of codes until you don't have the crash anymore. Commented Aug 8, 2014 at 13:17
  • 2
    In addition to Valgrind, Coverity and cppcheck, you should add Asan and UBsan to your testing regime. If your code is corss-platofrm, then add Microsoft's Enterprise Analysis (/analyze) and Apple's Malloc and Scribble guards, too. You should also use as many compilers as possible using as many standards as possible because compiler warnings are a diagnostic and they get better over time. There is no silver bullet, and one size does not fit all. The more tools and compilers you use, the more complete the coverage because each tools has its strengths and weaknesses. Commented Jun 15, 2016 at 1:25