aboutsummaryrefslogtreecommitdiff
path: root/binutils/demanguse.c
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2023-06-16 14:48:54 +0100
committerAndrew Burgess <aburgess@redhat.com>2023-07-17 09:45:19 +0100
commitd3a2163ee2d1d6487f5a3ce28b842b64dbd85d8d (patch)
treee2d3dae4fd4ee8f9b981cd31e6c75266d884a30e /binutils/demanguse.c
parenta068d1a6b2dd982e1019bc265610f07bb8adff94 (diff)
downloadgdb-d3a2163ee2d1d6487f5a3ce28b842b64dbd85d8d.zip
gdb-d3a2163ee2d1d6487f5a3ce28b842b64dbd85d8d.tar.gz
gdb-d3a2163ee2d1d6487f5a3ce28b842b64dbd85d8d.tar.bz2
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.
Diffstat (limited to 'binutils/demanguse.c')
0 files changed, 0 insertions, 0 deletions