This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Problematic .gdb_index warning regexps in testsuite
- From: dje at google dot com (Doug Evans)
- To: gdb at sourceware dot org
- Date: Thu, 19 Apr 2012 08:11:45 -0700 (PDT)
- Subject: Problematic .gdb_index warning regexps in testsuite
Hi.
While grepping for gdb_index in the testsuite I found this:
gdb.base/annota1.exp: -re "\r\n\032\032post-prompt\r\nStarting program: $binexp \(\r\nwarning: Skipping \[^\r\n\]+ .gdb_index section in \[^\r\n\]+\)?\(\(\r\n\r\n\032\032frames-invalid\)|\(\r\n\r\n\032\032breakpoints-invalid\)\)+\r\n\r\n\032\032starting\(\(\r\n\r\n\032\032frames-invalid\)|\(\r\n\r\n\032\032breakpoints-invalid\)\)*\r\n\r\n\032\032breakpoint 1\r\n\r\nBreakpoint 1, \r\n\032\032frame-begin 0 $hex\r\n\r\n\032\032frame-function-name\r\nmain\r\n\032\032frame-args\r\n \\(\\)\r\n\032\032frame-source-begin\r\n at \r\n\032\032frame-source-file\r\n.*annota1.c\r\n\032\032frame-source-file-end\r\n:\r\n\032\032frame-source-line\r\n$main_line\r\n\032\032frame-source-end\r\n\r\n\r\n\032\032source.*$srcfile:$main_line:.*:beg:$hex\r\n\r\n\032\032frame-end\r\n\r\n\032\032stopped.*$gdb_prompt$" {
gdb.base/async-shell.exp:set gdbindex_warning_re "warning: Skipping \[^\r\n\]+ \\.gdb_index section \[^\r\n\]*"
lib/mi-support.exp:set gdbindex_warning_re "&\"warning: Skipping \[^\r\n\]+ \.gdb_index section in \[^\"\]+\"\r\n"
I think we don't want to go down this path.
This will just proliferate, and make tests unnecessarily bulkier
(harder to maintain) than they should be.
I don't have a patch.
Just thought I'd point it out.