From d3a2163ee2d1d6487f5a3ce28b842b64dbd85d8d Mon Sep 17 00:00:00 2001 From: Andrew Burgess Date: Fri, 16 Jun 2023 14:48:54 +0100 Subject: [PATCH] gdb/testsuite: remove use of sleep from gdb.base/foll-vfork.exp While working on gdb.base/foll-vfork.exp I noticed that there are several random 'sleep' calls throughout the test. The comment suggests these are to allow for output from a vforked child to arrive, but in each case the test is about to close and restart GDB, so I don't see how random output from a child process could impact testing. I removed the sleep calls and couldn't reproduce any failures from this test, I left the test running for a couple of hours, and tried loading my machine, and the test seems fine with these removed. I've left this as a separate commit so that if, in the future, someone can show that these are required, it will be easy to revert this one patch and bring them back. There should be no change in what is tested after this commit. --- gdb/testsuite/gdb.base/foll-vfork.exp | 48 --------------------------- 1 file changed, 48 deletions(-) diff --git a/gdb/testsuite/gdb.base/foll-vfork.exp b/gdb/testsuite/gdb.base/foll-vfork.exp index d847487fd66..13b8c3537a1 100644 --- a/gdb/testsuite/gdb.base/foll-vfork.exp +++ b/gdb/testsuite/gdb.base/foll-vfork.exp @@ -105,12 +105,6 @@ proc_with_prefix vfork_parent_follow_through_step { binfile srcfile } { pass $gdb_test_name } } - - # The child has been detached; allow time for any output it might - # generate to arrive, so that output doesn't get confused with - # any gdb_expected debugger output from a subsequent testpoint. - # - exec sleep 1 } proc_with_prefix vfork_parent_follow_to_bp { binfile srcfile } { @@ -127,12 +121,6 @@ proc_with_prefix vfork_parent_follow_to_bp { binfile srcfile } { pass $gdb_test_name } } - - # The child has been detached; allow time for any output it might - # generate to arrive, so that output doesn't get confused with - # any expected debugger output from a subsequent testpoint. - # - exec sleep 1 } proc_with_prefix vfork_child_follow_to_exit { binfile srcfile } { @@ -148,12 +136,6 @@ proc_with_prefix vfork_child_follow_to_exit { binfile srcfile } { pass $gdb_test_name } } - - # The parent has been detached; allow time for any output it might - # generate to arrive, so that output doesn't get confused with - # any gdb_expected debugger output from a subsequent testpoint. - # - exec sleep 1 } proc_with_prefix vfork_and_exec_child_follow_to_main_bp { binfile srcfile } { @@ -168,12 +150,6 @@ proc_with_prefix vfork_and_exec_child_follow_to_main_bp { binfile srcfile } { pass $gdb_test_name } } - - # The parent has been detached; allow time for any output it might - # generate to arrive, so that output doesn't get confused with - # any gdb_expected debugger output from a subsequent testpoint. - # - exec sleep 1 } proc_with_prefix vfork_and_exec_child_follow_through_step { binfile srcfile } { @@ -189,12 +165,6 @@ proc_with_prefix vfork_and_exec_child_follow_through_step { binfile srcfile } { pass $gdb_test_name } } - - # The parent has been detached; allow time for any output it might - # generate to arrive, so that output doesn't get confused with - # any expected debugger output from a subsequent testpoint. - # - exec sleep 1 } proc continue_to_vfork {} { @@ -228,12 +198,6 @@ proc_with_prefix tcatch_vfork_then_parent_follow { binfile srcfile } { exp_continue } } - - # The child has been detached; allow time for any output it might - # generate to arrive, so that output doesn't get confused with - # any expected debugger output from a subsequent testpoint. - # - exec sleep 1 } proc_with_prefix tcatch_vfork_then_child_follow_exec { binfile srcfile } { @@ -260,12 +224,6 @@ proc_with_prefix tcatch_vfork_then_child_follow_exec { binfile srcfile } { pass "$gdb_test_name (followed exec)" } } - - # The parent has been detached; allow time for any output it might - # generate to arrive, so that output doesn't get confused with - # any expected debugger output from a subsequent testpoint. - # - exec sleep 1 } proc tcatch_vfork_then_child_follow_exit { binfile srcfile } { @@ -290,12 +248,6 @@ proc tcatch_vfork_then_child_follow_exit { binfile srcfile } { exp_continue } } - - # The parent has been detached; allow time for any output it might - # generate to arrive, so that output doesn't get confused with - # any expected debugger output from a subsequent testpoint. - # - exec sleep 1 } proc_with_prefix vfork_relations_in_info_inferiors { variant binfile srcfile non_stop } { -- 2.30.2