From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9611 invoked by alias); 19 Apr 2012 15:12:10 -0000 Received: (qmail 9564 invoked by uid 22791); 19 Apr 2012 15:12:09 -0000 X-SWARE-Spam-Status: No, hits=-4.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-vb0-f73.google.com (HELO mail-vb0-f73.google.com) (209.85.212.73) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 19 Apr 2012 15:11:49 +0000 Received: by vbbfc26 with SMTP id fc26so1010461vbb.0 for ; Thu, 19 Apr 2012 08:11:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=to:subject:message-id:date:from:x-gm-message-state; bh=ncbVFzbeV0Al3erhkioTRClHstcN3BV9CWm7CDWKoYw=; b=XJDq9cB0xrQmG6BXHcaiym3aKUg7avwz1iAa0pY/8T9uclIbS64Ix0VqnJQPH52V3G qDOPviHx0bApECwZrMuOme84nDtBuIKE68O1gBge4osKCxPHteHR8qHwHSn2Wlqceipx GirGSMvDdJzvvq+8pHgcVKT0g7AIAjS3whYI9P1uxn+ZauvU4JEIx2DsFtkj6VRiScIK Qq3rcz7EWT+POEwS+WiRBuwmUgyYWyFebo/ik8J82YQn9SZyAiONS093S4nHVcR2lxDA xS8DRXz6qQAyoqcwYRt2YFwEwjR+40b0KI31dvxwhq3M8XgzfVS+HntBSCsD6gNVo+GJ j+2g== Received: by 10.101.121.13 with SMTP id y13mr884447anm.3.1334848305792; Thu, 19 Apr 2012 08:11:45 -0700 (PDT) Received: by 10.101.121.13 with SMTP id y13mr884441anm.3.1334848305714; Thu, 19 Apr 2012 08:11:45 -0700 (PDT) Received: from wpzn4.hot.corp.google.com (216-239-44-65.google.com [216.239.44.65]) by gmr-mx.google.com with ESMTPS id y53si2433482yhe.4.2012.04.19.08.11.45 (version=TLSv1/SSLv3 cipher=AES128-SHA); Thu, 19 Apr 2012 08:11:45 -0700 (PDT) Received: from ruffy.mtv.corp.google.com (ruffy.mtv.corp.google.com [172.18.110.50]) by wpzn4.hot.corp.google.com (Postfix) with ESMTP id 97CF11E004D for ; Thu, 19 Apr 2012 08:11:45 -0700 (PDT) Received: by ruffy.mtv.corp.google.com (Postfix, from userid 67641) id 315F72461B1; Thu, 19 Apr 2012 08:11:45 -0700 (PDT) To: gdb@sourceware.org Subject: Problematic .gdb_index warning regexps in testsuite Message-Id: <20120419151145.315F72461B1@ruffy.mtv.corp.google.com> Date: Thu, 19 Apr 2012 15:12:00 -0000 From: dje@google.com (Doug Evans) X-Gm-Message-State: ALoCoQktGDw7+p3MkWlqpD6jpTfKGwwMS1xE8yxOE8jWBkmy9QHHPnJRNISZ+tX123YWgEVBZwU2M8Nfeqp+nagE47zJA6AdYJHz8XRb9QI0RwYzoOO02tYPrL3eV23HNMjQZGTf5fec9ExITHwMY/faXFK8aCqO/w== X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-04/txt/msg00153.txt.bz2 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.