gdb/testsuite: Match file size in gdb.debuginfod/crc_mismatch.exp

gdb's debuginfod progress messages include the size of the file being
downloaded if the size information is available at the time the message
is printed.  For example:

    Downloading 10 MB separate debug info for /lib64/libxyz.so

This size information is omitted if it's not available at the time of
printing:

    Downloading separate debug info for /lib64/libxyz.so

A pattern in crc_mismatch.exp fails to be matched if a progress message
includes a file size.  Add a wildcard to the pattern so that it matches
the progress message whether or not it includes the file size.
This commit is contained in:
Aaron Merey
2023-05-11 12:38:12 -04:00
parent 6e96d8a970
commit b7ea736a38

View File

@@ -97,7 +97,7 @@ proc_with_prefix local_debuginfod { } {
gdb_test "file [standard_output_file crc_mismatch-2]" \
[multi_line \
"Reading symbols from ${escapedobjdirsubdir}/crc_mismatch-2\\.\\.\\." \
"Downloading separate debug info for ${escapedobjdirsubdir}/crc_mismatch-2\\.\\.\\." \
"Downloading.*separate debug info for ${escapedobjdirsubdir}/crc_mismatch-2\\.\\.\\." \
"Reading symbols from ${cache}/\[^\r\n\]+\\.\\.\\.(?:\r\nExpanding full symbols from \[^\r\n\]+)*"] \
"debuginfod running, info downloaded, no CRC mismatch"
}