Re: [PATCH] Fix "spawn id XYZ not open" errors in gdb.mi/mi-exec-run.exp

[Keith Seitz <keiths@redhat.com>]

On 2/28/22 09:32, Andrew Burgess wrote:
> Keith Seitz via Gdb-patches <gdb-patches@sourceware.org> writes:
> 
>> [1] Anyone know why this test doesn't simply use gdb_test_multiple? I can only
>> assume that it was intentionally written this way, and I've modified the code with
>> that assumption. I have tested a version using gdb_test_multiple, and that appears
>> to work fine, too, if that is preferred. [It still employs exp_continue to fix the
>> spawn_id errors.]
> 
> As the reasoning isn't discussed in the .exp file, the commit message,
> or in the original mailing list thread, I'd assume it was just an
> oversight.  If you see the same pass/fail using the gdb_test_multiple,
> then I think it woud be a nice cleanup to switch over.

I've tried testing this a bit more, and it looks like gdb_test_multiple
"interferes" with the testing because of all the built-in matches. So we see
"spurious" (as far as this test is concerned) "Process no longer exists" errors,
and these end up racy between runs.

So in that case, I will retract the gdb_test_multiple bit. I wonder if this
was discussed this on IRC in the distant past?

Thanks for the review!

Keith