[Minios-devel] [UNIKRAFT PATCH] doc: fix two issues in the debugging guide

[Hugo Lefeuvre <hugo.lefeuvre@xxxxxxxxx>]

+ use continue instead of run after setting the hw breakpoint: the
  debugging session is typically already running at this stage
+ uk trace save instead of uk save

Signed-off-by: Hugo Lefeuvre <hugo.lefeuvre@xxxxxxxxx>
---
 doc/guides/developers-debugging.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/guides/developers-debugging.rst 
b/doc/guides/developers-debugging.rst
index b80a39b..f7c8e74 100644
--- a/doc/guides/developers-debugging.rst
+++ b/doc/guides/developers-debugging.rst
@@ -63,7 +63,7 @@ connect gdb by using the debug image with: ::
 Unless you're debugging early boot code (until ``_libkvmplat_start32``), 
you'll need to set a hardware break point: ::
 
   hbreak [location]
-  run
+  continue
 
 We'll now need to set the right CPU architecture: ::
 
@@ -188,7 +188,7 @@ buffer. You can print them by issuing the `gdb` command 
``uk trace``: ::
 Alternatively, you can save all trace data to disk with
 ``uk trace save <filename>``: ::
 
-  (gdb) uk save traces.dat
+  (gdb) uk trace save traces.dat
 
 .. note:: It may make sense to connect with `gdb` after the guest execution has
          been finished (and the trace buffer got filled). For this purpose,
-- 
2.7.4


_______________________________________________
Minios-devel mailing list
Minios-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/minios-devel