diff options
author | Thibault Saunier <tsaunier@gnome.org> | 2016-12-01 16:10:42 -0300 |
---|---|---|
committer | Thibault Saunier <tsaunier@gnome.org> | 2016-12-02 20:04:33 -0300 |
commit | 6203e3ae349f36d6fd744f55d597d436ddd2a36e (patch) | |
tree | 6a58cca33eac282fd054a195df8c8b402b14fa6f /mesontest.py | |
parent | 3d05b91e37ecab37d6cb70e9dfe827c4d4b52f18 (diff) | |
download | meson-6203e3ae349f36d6fd744f55d597d436ddd2a36e.zip meson-6203e3ae349f36d6fd744f55d597d436ddd2a36e.tar.gz meson-6203e3ae349f36d6fd744f55d597d436ddd2a36e.tar.bz2 |
mesontest: Let user work with gdb when not running in a loop
In the normal case the user probably wants to set break point or
anything when running an app in gdb, we should let him a chance to
do so.
In the case he is running in a loop, it probably means he want to
reproduce a crash or a race inside gdb so we should just go and
run in gdb.
We probably miss a few options to give him more control.
Diffstat (limited to 'mesontest.py')
-rwxr-xr-x | mesontest.py | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/mesontest.py b/mesontest.py index 8ec30e1..65b4159 100755 --- a/mesontest.py +++ b/mesontest.py @@ -382,9 +382,11 @@ class TestHarness: for i in range(self.options.repeat): print('Running: %s %d/%d' % (t.name, i+1, self.options.repeat)) if self.options.gdb: - wrap = ['gdb', '--quiet', '-ex', 'run', '-ex', 'quit'] + wrap = ['gdb', '--quiet'] if len(t.cmd_args) > 0: wrap.append('--args') + if self.options.repeat > 1: + wrap.append('-ex', 'run', '-ex', 'quit') res = self.run_single_test(wrap, t) else: |