[Bug server/30574] hang when using remote target, schedule-multiple, follow-fork-mode child, and stepping over a vfork

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30574

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a068d1a6b2dd982e1019bc265610f07bb8adff94

commit a068d1a6b2dd982e1019bc265610f07bb8adff94
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Wed Jun 21 14:19:27 2023 +0100

    gdb/testsuite: expand gdb.base/foll-vfork.exp

    This commit provides tests for all of the bugs fixed in the previous
    four commits, this is achieved by expanding gdb.base/foll-vfork.exp to
    run with different configurations:

      * target-non-stop on/off
      * non-stop on/off
      * schedule-multiple on/off

    We don't test with schedule-multiple on if we are using a remote
    target, this is due to bug gdb/30574.  I've added a link to that bug
    in this commit, but all this commit does is expose that bug, there's
    no fixes here.

    Some of the bugs fixed in the previous commits are very timing
    dependent, as such, they don't always show up.  I've had more success
    when running this test on a very loaded machine -- I usually run ~8
    copies of the test in parallel, then the bugs would normally show up
    pretty quickly.

    Other than running the test in more configurations, I've not made any
    changes to what is actually being tested, other than in one place
    where, when testing with non-stop mode, GDB stops in a different
    inferior, as such I had to add a new 'inferior 2' call, this can be
    found in vfork_relations_in_info_inferiors.

    I have cleaned things up a little, for example, making use of
    proc_with_prefix to remove some with_test_prefix calls.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30574

-- 
You are receiving this mail because:
You are on the CC list for the bug.