diff options
| author | Tom de Vries <tdevries@suse.de> | 2024-10-22 09:23:26 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2024-10-22 09:23:26 +0200 |
| commit | a03c03f84ac331a1ae03fbf1d7e53001935e45be (patch) | |
| tree | 5eada7be2ce872ca2ff32531ed66d4c8d9c4fcf6 /gdb/python/py-finishbreakpoint.c | |
| parent | 485d9cab65acb49838c9c6e5df7fa9ebfcfceaf9 (diff) | |
| download | gdb-a03c03f84ac331a1ae03fbf1d7e53001935e45be.zip gdb-a03c03f84ac331a1ae03fbf1d7e53001935e45be.tar.gz gdb-a03c03f84ac331a1ae03fbf1d7e53001935e45be.tar.bz2 | |
[gdb/testsuite] Handle maint set dwarf synchronous off default
I ran the testsuite with a patch setting dwarf_synchronous to false by
default, and ran into FAILs in test-cases gdb.dwarf2/dw2-inter-cu-error.exp
and gdb.dwarf2/dw2-inter-cu-error-2.exp, because the expected DWARF errors did
not show up as a result of the file command.
Fix this by forcing "maint set dwarf synchronous on".
Add the same in gdb.base/index-cache.exp, where this is also required.
Tested on aarch64-linux.
Diffstat (limited to 'gdb/python/py-finishbreakpoint.c')
0 files changed, 0 insertions, 0 deletions