diff options
| author | Tom Tromey <tom@tromey.com> | 2023-01-25 10:00:58 -0700 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2023-01-26 18:28:31 -0700 |
| commit | d6acf25c03f8c507e134f7438bd4360464ce111e (patch) | |
| tree | 013db4cf84afd5f7202a35e3b595e89de246146d /gdb/testsuite/gdb.mi/mi-cmd-error.exp | |
| parent | 306e12673e49e32f1e64d9dca7a30fe8add42e1c (diff) | |
| download | binutils-d6acf25c03f8c507e134f7438bd4360464ce111e.zip binutils-d6acf25c03f8c507e134f7438bd4360464ce111e.tar.gz binutils-d6acf25c03f8c507e134f7438bd4360464ce111e.tar.bz2 | |
Start gdb after building executable in mi-basics.exp
A lot of the MI tests start gdb and only then build the executable.
This just seemed weird to me, so I've fixed this up. In this patch,
no other cleanups are done, the startup is just moved to a more
logical (to me) spot.
Diffstat (limited to 'gdb/testsuite/gdb.mi/mi-cmd-error.exp')
0 files changed, 0 insertions, 0 deletions