espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-06-30 09:09:16 +08:00
Code Issues Packages Projects Releases Wiki Activity

[gdb/testsuite] Fix gdb.threads/fork-plus-threads.exp timeout with check-run1

Browse Source 
With gdb.threads/fork-plus-threads.exp and check-run1 we get:
...
FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: \
  inferior 1 exited (timeout)
...

Fix this by calling exp_continue for new thread and thread exited messages.

Tested on x86_64-linux.

gdb/testsuite/ChangeLog:

2019-08-01  Tom de Vries  <tdevries@suse.de>

	PR testsuite/24863
	* gdb.threads/fork-plus-threads.exp: Fix check-run1 timeout by
	calling exp_continue for new thread and thread exited messages.
This commit is contained in:
Tom de Vries
2019-08-01 10:48:11 +02:00
parent 2a3ad588e0
commit 59bd512b9c
2 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,9 @@
2019-08-01 Tom de Vries <tdevries@suse.de>
PR testsuite/24863
* gdb.threads/fork-plus-threads.exp: Fix check-run1 timeout by
calling exp_continue for new thread and thread exited messages.
2019-08-01 Tom de Vries <tdevries@suse.de> 2019-08-01 Tom de Vries <tdevries@suse.de>
PR testsuite/24863 PR testsuite/24863

8
gdb/testsuite/gdb.threads/fork-plus-threads.exp
View File

@ -87,6 +87,14 @@ proc do_test { detach_on_fork } {
set saw_thread_stopped 1 set saw_thread_stopped 1
exp_continue exp_continue
} }
-re "Thread \[^\r\n\]+ exited" {
# Avoid timeout with check-read1
exp_continue
}
-re "New Thread \[^\r\n\]+" {
# Avoid timeout with check-read1
exp_continue
}
-re "Inferior 1 \(\[^\r\n\]+\) exited normally" { -re "Inferior 1 \(\[^\r\n\]+\) exited normally" {
pass $test pass $test
} }