--skip-wait-for-start makes certain files not to stop more than once

[vagoston]

The test case below is and should be successful, but if you add --skip-wait-for-start to the cmd at rd_test_base.rb:33, it will fail, since the last assert fails.
My experience with this flag is that debase will not stop any of the files that are in the stacktrace when the program stops for the first time, but other files are still functioning normally.

    create_socket ["sleep 1", "puts 'one'", "puts 'two'"]
    send_test_breakpoint(2)
    assert_breakpoint_added_no(1)
    start_debugger
    assert_test_breakpoint(2)
    send_test_breakpoint(3)
    assert_breakpoint_added_no(2)
    send_next # test:1 -> test2:4
    assert_test_breakpoint(3)
    send_cont # test2:4 -> test:3

[vagoston]

Closing this one, this issue is not specific to --skip-wait-for-start