title: How to make good use of stack trace (from kernel or core dump)?
body: <p>If you are lucky when your kernel module crashes, you would get an oops with a log with a lot of information, such as values in the registers etc. One such information is the stack trace (The same is true for core dumps, but I had originally asked this for kernel modules). Take this example:</p>
  
  <pre><code>[&lt;f97ade02&gt;] ? skink_free_devices+0x32/0xb0 [skin_kernel]
  [&lt;f97aba45&gt;] ? cleanup_module+0x1e5/0x550 [skin_kernel]
  [&lt;c017d0e7&gt;] ? __stop_machine+0x57/0x70
  [&lt;c016dec0&gt;] ? __try_stop_module+0x0/0x30
  [&lt;c016f069&gt;] ? sys_delete_module+0x149/0x210
  [&lt;c0102f24&gt;] ? sysenter_do_call+0x12/0x16
  </code></pre>
  
  <p>My guess is that the <code>+&lt;number1&gt;/&lt;number2&gt;</code> has something to do with the offset from function in which the error has occurred. That is, by inspecting this number, perhaps looking at the assembly output I should be able to find out the line (better yet, instruction) in which this error has occurred. Is that correct?</p>
  
  <p>My question is, what are these two numbers exactly? How do you make use of them?</p>