Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2019-10-12,master

commit 885b7d1c42afedf634c1fb6b2cb1ed4c0622b65a Author: Sven Eckelmann sven@narfation.org Date: Sat Oct 12 00:10:18 2019 +0000

doc: open-mesh/Emulation_Debug

885b7d1c42afedf634c1fb6b2cb1ed4c0622b65a open-mesh/Emulation_Debug.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/open-mesh/Emulation_Debug.textile b/open-mesh/Emulation_Debug.textile index 1538479..fc6bf14 100644 --- a/open-mesh/Emulation_Debug.textile +++ b/open-mesh/Emulation_Debug.textile @@ -382,9 +382,9 @@ wireshark -k -i remote-dump

h2. Using GDB

-The instances are listening on 127.0.0.1 TCP port <code>23000 + instance_no</code>. We will use in the following example instance 1. The gdb debugger can be started from the linux source directory and all <code>lx-*</code> helpers will be automatically be loaded. +The instances are listening on 127.0.0.1 TCP port <code>23000 + instance_no</code>. We will use in the following example instance 1. The gdb debugger can be started from the linux source directory and all <code>lx-*</code> helpers will automatically be loaded.

-The debugging with gdb can be started from the linux-next directory: +The debugging session with gdb can be started from the linux-next directory:

<pre> $ gdb -iex "set auto-load safe-path scripts/gdb/" -ex 'target remote 127.0.0.1:23001' -ex c ./vmlinux