title: Interview question about debugging, multithreading
body: <p>I had telephone interview question yesterday.
  The interviewer asked me if I had faced any challenging debugging issue?
  I told him I once faced a problem debugging someone else's code and it took me 3-4 days to solve that. I used Windbg, symbols and a crash dump to solve the problem.</p>
  
  <p>Now is this enough to tell?  What is interviewer expecting?</p>
  
  <p>I don't know what else to tell, I faced that problem quite some time back and can't explain all details...</p>
  
  <p>This question is very very common and I am not sure what the right answer to it?</p>
  
  <p>One more question that is very common:</p>
  
  <p>Have you worked on multi-threaded applications? How can you find out deadlock?
  Answer: Well to find deadlock we can look at snapshot of process in memory and can look at threads that are waiting.</p>
  
  <p>Then next question: What can you do to avoid deadlock?</p>
  
  <ol>
  <li>Use waitformultipleobjects</li>
  <li>Maintain sequence of critical sections</li>
  </ol>
  
  <p>What do you guys say?</p>