diff options
Diffstat (limited to 'docs/gettingstarted/developers/gdb_examples.rst')
| -rw-r--r-- | docs/gettingstarted/developers/gdb_examples.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/gettingstarted/developers/gdb_examples.rst b/docs/gettingstarted/developers/gdb_examples.rst index 8ea34cbc276..8a0fb33e2a8 100644 --- a/docs/gettingstarted/developers/gdb_examples.rst +++ b/docs/gettingstarted/developers/gdb_examples.rst @@ -10,7 +10,7 @@ In this section we have a few useful gdb commands. Starting GDB ---------------------------- -Once at the gdb prompt, VPP can be started by isuuing the following commands: +Once at the gdb prompt, VPP can be started by running the following commands: .. code-block:: console @@ -24,7 +24,7 @@ Once at the gdb prompt, VPP can be started by isuuing the following commands: Backtrace ---------------------------- -If you encounter issues when running VPP, such as VPP terminating due to a segfault +If you encounter errors when running VPP, such as VPP terminating due to a segfault or abort signal, then you can run the VPP debug binary and then execute **backtrace** or **bt**. .. code-block:: console @@ -38,12 +38,12 @@ or abort signal, then you can run the VPP debug binary and then execute **backtr Get to the GDB prompt --------------------------------------- -When VPP is running, you can get to the command prompt by entering CTRL-c. +When VPP is running, you can get to the command prompt by pressing **CTRL+C**. Breakpoints --------------------------------------- -When at the GDB prompt, set a breakpoint by using the commands below: +When at the GDB prompt, set a breakpoint by running the commands below: .. code-block:: console |