This method of the dbgeng debugger driver used to just "pass", as setting
dbgeng free running still leads to numerous errors. This wasn't a problem
in the past because, as it turns out, nothing called the go method.
However, a recent refactor uses it.
Rather than launch dbgeng free running, instead have it single step one
step forwards. This is slow, but it makes progress, where previously we
weren't.
Differential Revision: https://reviews.llvm.org/D91737
self.step_info = res
def go(self):
- # We never go -- we always single step.
- pass
+ # FIXME: running freely doesn't seem to reliably stop when back in a
+ # relevant source file -- this is likely to be a problem when setting
+ # breakpoints. Until that's fixed, single step instead of running
+ # freely. This isn't very efficient, but at least makes progress.
+ self.step()
def _get_step_info(self, watches, step_index):
frames = self.step_info