We do not need to verify a current breakpoint, nor do a redundant check
on whether we have been asked to manually halt. Assume trapWait has done
its due diligence and stop the world once it returns.

Also, kill whitespace to make code appear more as a singular block for
readability.

Major source cleanup, still not finished. Removes gross control flow.

Instead of fighting against the normal flow, just signal a SIGTRAP and
let the existing flow handle it, as long as we set the halt flag
correctly the system should halt.

Fixes #95

* Cleanup comments
* Cleanup naming in certain instances
* Modify stacktrace to return current location

additionally fixes a bug when Detach is called on an exiting/exited thread: dbp.CurrentThread could point to a thread that has already been removed from dbp.Threads by trapWait which will lead to a nil pointer dereference caused proc.Process.clearBreakpoint getting nil from dbp.Threads[tid]

Fixes #154

On a thread that's leader of its group,
that is ptraced and that was survived by its children.

For hardware breakpoints we have to set them on every thread. It could
be the case that another thread is running. Stop it first, set the
breakpoint, then continue it.