diff options
| author | Tom de Vries <tdevries@suse.de> | 2023-02-28 15:50:23 +0100 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2023-02-28 15:50:23 +0100 |
| commit | 0c132dac7f21062f19d47982697f0a223ad430ed (patch) | |
| tree | 911a521c387e2911374128134188c7b87881ab37 /gdb/testsuite/gdb.python/py-breakpoint.c | |
| parent | eae679b9c7760e994c85695946c6b69a227dc69b (diff) | |
| download | binutils-0c132dac7f21062f19d47982697f0a223ad430ed.zip binutils-0c132dac7f21062f19d47982697f0a223ad430ed.tar.gz binutils-0c132dac7f21062f19d47982697f0a223ad430ed.tar.bz2 | |
[gdb/testsuite] Fix gdb.python/py-breakpoint.exp timeouts
On powerpc64le-linux, I run into two timeouts:
...
FAIL: gdb.python/py-breakpoint.exp: test_watchpoints: \
Test watchpoint write (timeout)
FAIL: gdb.python/py-breakpoint.exp: test_bkpt_internal: \
Test watchpoint write (timeout)
...
In this case, hw watchpoints are not supported, and using sw watchpoints
is slow.
Most of the time is spent in handling a try-catch, which triggers a malloc. I
think this bit is more relevant for the "catch throw" part of the test-case,
so fix the timeouts by setting the watchpoints after the try-catch.
Tested on x86_64-linux and powerpc64le-linux.
Diffstat (limited to 'gdb/testsuite/gdb.python/py-breakpoint.c')
| -rw-r--r-- | gdb/testsuite/gdb.python/py-breakpoint.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.python/py-breakpoint.c b/gdb/testsuite/gdb.python/py-breakpoint.c index 0f791da..1fb3416 100644 --- a/gdb/testsuite/gdb.python/py-breakpoint.c +++ b/gdb/testsuite/gdb.python/py-breakpoint.c @@ -60,6 +60,8 @@ int main (int argc, char *argv[]) /* Nothing. */ } + i = -1; /* Past throw-catch. */ + for (i = 0; i < 10; i++) { result += multiply (foo); /* Break at multiply. */ |