diff options
| author | Alan Hayward <alan.hayward@arm.com> | 2019-03-27 10:58:57 +0000 |
|---|---|---|
| committer | Alan Hayward <alan.hayward@arm.com> | 2019-03-27 11:51:15 +0000 |
| commit | 933aebfae6b1a2b83c3eb958ebf6e43fc7fdaed1 (patch) | |
| tree | 0bec1bd0d39694a8896d314376bf67cdd40f6ae2 /opcodes/mep-desc.c | |
| parent | 4c4849b9ed8c6dd7e1f822e1e395b62059ba7680 (diff) | |
| download | gdb-933aebfae6b1a2b83c3eb958ebf6e43fc7fdaed1.zip gdb-933aebfae6b1a2b83c3eb958ebf6e43fc7fdaed1.tar.gz gdb-933aebfae6b1a2b83c3eb958ebf6e43fc7fdaed1.tar.bz2 | |
Testsuite: Ensure interrupt-daemon-attach doesn't run forever
Looking at the AArch64 buildbot, I noticed about two dozen old instances of
interrupt-daemon-attach taking up a full 100% cpu each.
If the test fails then the test binary relies on an alarm to ensure it dies
after 60 seconds.
As per the Linux man page for alarm:
Alarms created by alarm() ... are not inherited by children created via fork.
Update the test to add an alarm in the child and also put a sleep in the
child loop so it does not constantly consume cpu.
Note I haven't managed to re-create why the test failed. This fix will just
stop it hanging and consuming cpu when it does.
gdb/testsuite/ChangeLog:
* gdb.base/interrupt-daemon-attach.c (main): Add alarm and sleep
in child.
Diffstat (limited to 'opcodes/mep-desc.c')
0 files changed, 0 insertions, 0 deletions