From https://github.com/xdebug/xdebug/pull/890#issue-1728778608:

It seems that the step_over command to stop is not a good behavior in other coroutines, unless this coroutine is destroyed.
For example:

<?php

use Swoole\Coroutine;

use function Swoole\Coroutine\run;

require __DIR__ . '/vendor/autoload.php';

run(function () {
    $a = 1; // position 1
    Coroutine::create(function () {
        $a = 1; // position 2
        Coroutine::sleep(1);
        $a = 1;
    });
    Coroutine::create(function () {
        $a = 1;
        Coroutine::sleep(1);
        $a = 1;
    });
    Coroutine::create(function () {
        $a = 1;
    });
    $b = 1; // position 3
});
$a = 1;

Assuming the program stops at position 1, if I execute the "step_over" command, the program will stop at position 2 (If I want the program to stop at position 2, I think this is what the 'step_into' command should do). According to my understanding, the program should not stop inside any coroutine and should stop at position 3. Currently, the behavior of xdebug in handling the "step_over" command causes erratic behavior when there is an IO switch in a coroutine.