title: Need suggestions with Seg fault debugging
body: <p>I am working on this old c++ program that runs in Linux. It is the worst code I had ever tried to read, and running it with ValGrind gives tons of memory problems. </p>
  
  <p>I want to pick off the seg faults one by one, but by the time ValGrind finds the line the code crashes on the damage has been done. This code uses third party libraries as well as home grown libraries. The third party libs can be trusted but not the home grown.</p>
  
  <p>Does anyone have any suggestions on how to find memory corruption that causes a seg fault? I have never had to find seg faults in someone else's code, especially code that was released with no documentation.</p>
  
  <p>Two things that I found out today was, the compiler settings were changed to NOT automatically init. values and the word sized changed from 32 to 64 bit.</p>
  
  <p>I'm at my witts end trying to make any headway, anyone have any deep memory analysis ideas?</p>
  
  <p>thanks</p>