Skip to content

Commit

Permalink
[docs] Fix gdb command for debugging (#233)
Browse files Browse the repository at this point in the history
  • Loading branch information
dayeol committed Mar 5, 2021
1 parent 0022215 commit 5a005c0
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/source/Getting-Started/How-to-Debug.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ From your `build` directory where you ran `make`, use:
All cores will immediately hang at the first instruction (i.e., bootrom), waiting for `gdb` to be attached.

Now, run a riscv `gdb` in another terminal. You can feed it with the
bbl binary or the kernel image to add debug information.
bbl binary or the kernel image to add debug information.


For example, if you want to debug with the `bbl` symbols
Expand Down Expand Up @@ -50,7 +50,7 @@ Try to set breakpoints and run.
Before setting breakpoints, you should run following command:

```
(gdb) set riscv use_compressed_breakpoints no
(gdb) set riscv use-compressed-breakpoints no
```

To see why we need that command, see [this issue](https://github.com/riscv/riscv-binutils-gdb/issues/106)
Expand Down

0 comments on commit 5a005c0

Please sign in to comment.