[pushed] gdb/testsuite: adjust ensure_gdb_index to cooked_index_functions::dump changes

Message ID 20230131164554.52680-1-simon.marchi@efficios.com
State Committed
Commit 95cbab2bebf7e810eded3e16ae7e82b13f4d2493
Headers
Series [pushed] gdb/testsuite: adjust ensure_gdb_index to cooked_index_functions::dump changes |

Commit Message

Simon Marchi Jan. 31, 2023, 4:45 p.m. UTC
  Following 7d82b08e9e0a ("gdb/dwarf: dump cooked index contents in
cooked_index_functions::dump"), I see some failures like:

    (gdb) mt print objfiles with-mf^M
    ^M
    Object file /home/smarchi/build/binutils-gdb/gdb/testsuite/outputs/gdb.base/with-mf/with-mf:  Objfile at 0x614000005040, bfd at 0x6120000e08c0, 18 minsyms    ^M
    ^M
    Cooked index in use:^M
    ^M
    ...
    (gdb) FAIL: gdb.base/with-mf.exp: check if index present

This is because the format of the "Cooked index in use" line changed
slightly.  Adjust ensure_gdb_index to expect the trailing colon.

Change-Id: If0a87575c02d8a0bc0d4b8ead540c234c62760f8
---
 gdb/testsuite/lib/gdb.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
  

Patch

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 0201c102fa7b..7f273bb91f72 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -8699,7 +8699,7 @@  proc ensure_gdb_index { binfile {style ""} } {
 	    set has_index 1
 	    gdb_test_lines "" $gdb_test_name ".*"
 	}
-	-re "\r\n(Cooked index in use|Psymtabs)(?=\r\n)" {
+	-re "\r\n(Cooked index in use:|Psymtabs)(?=\r\n)" {
 	    gdb_test_lines "" $gdb_test_name ".*"
 	}
 	-re ".gdb_index: faked for \"readnow\"" {