ligang/vpp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Finish event logger, viewer and cleanup.

Browse Source 
Change-Id: I3de038439bf0ab5755777c0f4930aec0514f5b63
Signed-off-by: John DeNisco <jdenisco@cisco.com>
This commit is contained in:
John DeNisco
2018-08-23 14:04:22 -04:00
committed by Damjan Marion
parent 33ed3e4c7d
commit 2ba9dcf408
17 changed files with 346 additions and 142 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/gettingstarted/developers/gdb_examples.rst
View File

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