gopc is the instruction of the `go` command that spawned this goroutine.
What we really want (unless we can get the PC from the thread) is the
value of sched.pc which is the value of the PC at the time it was
parked.

This fix helps avoid infinite recursion.

Fixes #192

bugfix, Issue #163: offset of g struct in TLS picked based on the value of runtime.buildVersion and presence of compile units created by GNU AS, instead of being fixed to -16

Allows a user to execute `dlv trace [regexp]` and Delve will execute the
program and output information on functions matching [regexp].

Finishes #63 #64

* Remove half baked CallFn implementation.
* Cleanup whitespace
* Cleanup read/write mem functions

Process is an incorrect name for the DebuggedProcess struct that the
thread is "a part" of. Also, no need to export that field.

* Properly find next source line for goroutines blocked in chanrecv
* Refactor breakpoint clearing
* Refactor temp breakpoint setting

* DebuggedProcess method: `PrintGoroutinesInfo` -> `GoroutinesInfo`
* `goroutines` command in command/command.go now responsible for
  printing info.

* Better tracking of current goroutine
* More efficient, eliminates superfluous step syscalls
* Handles concurrency and thread coordination better