title: How to interpret a GDB backtrace?
body: <pre><code>0x004069f1 in Space::setPosition (this=0x77733cee, x=-65, y=-49) at space.h:44    
  0x00402679 in Checkers::make_move (this=0x28cbb8, move=...) at checkers.cc:351
  0x00403fd2 in main_savitch_14::game::make_computer_move (this=0x28cbb8) at game.cc:153
  0x00403b70 in main_savitch_14::game::play (this=0x28cbb8) at game.cc:33
  0x004015fb in _fu0___ZSt4cout () at checkers.cc:96
  0x004042a7 in main () at main.cc:34
  </code></pre>
  
  <p>Hello, I am coding a game for a class and I am running into a segfault. The checker pieces are held in a two dimensional array, so the offending bit appears to be invalid x/y for the array. The moves are passed as strings, which are converted to integers, thus for the x and y were somehow ASCII NULL. I noticed that in the function call make_move it says move=...</p>
  
  <p>Why does it say move=...? Also, any other quick tips of solving a segfault? I am kind of new to GDB.</p>