The current gdb support launches gdb but doesn't start the daemon. If you start ovsdb-server with gdb, ovs-sandbox produces an error as it tries to run ovs-vsctl before ovsdb-server is running. Telling gdb to start the daemon immediately avoids this error.
There are cases where it's useful to go straight to the gdb prompt, too. For example, someone may want to set a breakpoint. In that case, it's easy enough to just kill it, set a breakpoint, and execute 'run' again. In passing, fix indentation to use spaces instead of tabs. Signed-off-by: Russell Bryant <rbry...@redhat.com> --- Note: This may produce a merge conflict with the ovn branch since I fixed the same indentation issue there in a different patch. --- tutorial/ovs-sandbox | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tutorial/ovs-sandbox b/tutorial/ovs-sandbox index 9520a41..251f021 100755 --- a/tutorial/ovs-sandbox +++ b/tutorial/ovs-sandbox @@ -35,8 +35,8 @@ rungdb() { # Use "DISPLAY" variable to determine out if X is supported if $under_gdb && [ "$DISPLAY" ]; then args=`echo $@ |sed s/--detach//g | sed s/--vconsole:off//g` - xterm_title=$1 - run_xterm $xterm_title gdb --args $args + xterm_title=$1 + run_xterm $xterm_title gdb -ex run --args $args else run $@ fi -- 2.1.0 _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev