3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-23 02:05:57 +01:00
Code Issues Releases Wiki Activity

readme: typos

Browse Source
This commit is contained in:
Ciro Santilli 六四事件 法轮功
2019-11-08 00:00:02 +00:00
parent 4c3b9c79a7
commit d4b7030366
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.adoc
View File

@@ -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