title: How to methodically trace the location of source code
body: <p>I often spend lots of time trying to find out where the exact implementation is located. It gets very frustrating when dealing with some low-level code that might end up somewhere in kernel.</p>
  
  <p>I usually just google or try to guess the location and/or method names, but it is not always very effective.</p>
  
  <p>Is there some methodical way to trace the flow up to the implementation? How do you guys usually do it?</p>