From d4b70303660fea625860b5071d02ebc75c259a47 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ciro=20Santilli=20=E5=85=AD=E5=9B=9B=E4=BA=8B=E4=BB=B6=20?= =?UTF-8?q?=E6=B3=95=E8=BD=AE=E5=8A=9F?= Date: Fri, 8 Nov 2019 00:00:02 +0000 Subject: [PATCH] readme: typos --- README.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.adoc b/README.adoc index f508fc0..fbdf630 100644 --- a/README.adoc +++ b/README.adoc @@ -9847,7 +9847,7 @@ You can still send key presses to QEMU however even without the mouse capture, j ==== Reverse debug the emulator -While step debugging any complext program, you always end up feeling the need to step in reverse to reach the last call to some function that was called before the failure point, in order to trace back the problem to the actual bug source. +While step debugging any complex program, you always end up feeling the need to step in reverse to reach the last call to some function that was called before the failure point, in order to trace back the problem to the actual bug source. While GDB "has" this feature, it is just too broken to be usable, and so we expose the amazing Mozilla RR tool conveniently in this repo: https://stackoverflow.com/questions/1470434/how-does-reverse-debugging-work/53063242#53063242 @@ -9873,9 +9873,9 @@ break qemu_add_opts continue .... -and you can now reiably use reverse debugging commands such as `reverse-continue`, `reverse-finish` and `reverse-next`! +and you can now reliably use reverse debugging commands such as `reverse-continue`, `reverse-finish` and `reverse-next`! -To restart debugging again after quitting `rr`, simlpy run on your host terminal: +To restart debugging again after quitting `rr`, simply run on your host terminal: .... rr replay