GNOME Bugzilla – Bug 796389
gst-validate-launcher: Stop in --gdb by default, add --gdb-non-stop
Last modified: 2018-05-25 11:22:05 UTC
This patch modifies the default behavior of --gdb to not run and quit automatically the debugee, but rather wait for user input. This is usually much more convenient to debug all kinds of bugs. The automatic run behavior has been moved to a new command switch: --gdb-non-stop
*** Bug 796390 has been marked as a duplicate of this bug. ***
Created attachment 372392 [details] [review] gst-validate-launcher: Stop in --gdb by default, add --gdb-non-stop This patch modifies the default behavior of --gdb to not run and quit automatically the debugee, but rather wait for user input. This is usually much more convenient to debug all kinds of bugs. The automatic run behavior has been moved to a new command switch: --gdb-non-stop
Review of attachment 372392 [details] [review]: ::: validate/launcher/main.py @@ +460,3 @@ action="store_true", help="Run the tests inside gdb (implies" " --output-dir=stdout and --jobs=1)") Is the test timeout UNLIMITED when this is used? @@ +463,3 @@ + parser.add_argument("--gdb-non-stop", dest="gdb_non_stop", + action="store_true", + help="Run the debugee automatically in gdb (implies --gdb)") debugee? "tests" ?
Created attachment 372398 [details] [review] gst-validate-launcher: Stop in --gdb by default, add --gdb-non-stop This patch modifies the default behavior of --gdb to not run and quit automatically the test, but rather wait for user input. This is usually much more convenient to debug all kinds of bugs. The automatic run behavior has been moved to a new command switch: --gdb-non-stop
Attachment 372398 [details] pushed as 2c32ccd - gst-validate-launcher: Stop in --gdb by default, add --gdb-non-stop