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.
This commit is contained in:
parent
3d05b91e37
commit
6203e3ae34
|
@ -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:
|
||||
|
|
Loading…
Reference in New Issue