projects / binutils-gdb.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 306e126) | patch
Start gdb after building executable in mi-basics.exp
authorTom Tromey <tom@tromey.com>
Wed, 25 Jan 2023 17:00:58 +0000 (10:00 -0700)
committerTom Tromey <tom@tromey.com>
Fri, 27 Jan 2023 01:28:31 +0000 (18:28 -0700)
commitd6acf25c03f8c507e134f7438bd4360464ce111e
tree013db4cf84afd5f7202a35e3b595e89de246146dtree
parent306e12673e49e32f1e64d9dca7a30fe8add42e1ccommit | diff
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.
gdb/testsuite/gdb.mi/mi-basics.exp diff | blob | history