Is `CaptureStackBackTrace` the way to go for this? I'm not sure whether that or `StackWalk64` is the "best interface." For comparison ruby uses `StackWalk64`, but they also spawn a thread to print a backtrace (probably because they only print during crashes I believe).

With debuginfo enabled we don't turn on frame pointer elimination, so we can just continue to only guarantee backtraces with debuginfo enabled. Unless LLVM is able to generate windows' preferred form of debuginfo, we're stuck with DWARF.