From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30529 invoked by alias); 17 Mar 2012 07:27:56 -0000 Received: (qmail 30518 invoked by uid 22791); 17 Mar 2012 07:27:55 -0000 X-SWARE-Spam-Status: No, hits=-6.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 17 Mar 2012 07:27:37 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q2H7RaXg008498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 17 Mar 2012 03:27:36 -0400 Received: from spoyarek.redhat.com (vpn1-5-20.ams2.redhat.com [10.36.5.20]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q2H7RUGb014972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sat, 17 Mar 2012 03:27:34 -0400 Date: Sat, 17 Mar 2012 07:27:00 -0000 From: Siddhesh Poyarekar To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] Fix gdb.base/auxv and gdb.base/cond-eval-mode test cases Message-ID: <20120317072843.GA25580@spoyarek.redhat.com> References: <20120316143002.GB22830@spoyarek.pnq.redhat.com> <4F63613A.4080501@redhat.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="G4iJoqBmSsgzjUCe" Content-Disposition: inline In-Reply-To: <4F63613A.4080501@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-03/txt/msg00648.txt.bz2 --G4iJoqBmSsgzjUCe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-length: 589 On Fri, Mar 16, 2012 at 03:50:18PM +0000, Pedro Alves wrote: > > * gdb.base/cond-eval-mode.exp: Fix the anticipated warning > > string > > > Please always send separate logical changes as separate emails, each with > its own subject line, description and patch. This part is obvious and > could have gone in immediately. > I have attached the cond-eval-mode.exp change here. I'll send another email for the ulimit change. -- Siddhesh testsuite/ChangeLog: 2012-03-16 Siddhesh Poyarekar * gdb.base/cond-eval-mode.exp: Fix the anticipated warning string --G4iJoqBmSsgzjUCe Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="fix-test-cases.patch" Content-length: 711 diff --git a/gdb/testsuite/gdb.base/cond-eval-mode.exp b/gdb/testsuite/gdb.base/cond-eval-mode.exp index dbbfc28..965c497 100644 --- a/gdb/testsuite/gdb.base/cond-eval-mode.exp +++ b/gdb/testsuite/gdb.base/cond-eval-mode.exp @@ -30,7 +30,7 @@ gdb_test_no_output $test_auto # If target-side condition evaluation is not supported, this warning will be # displayed. -set warning "warning: Target does not support breakpoint condition evaluation.\r\nUsing GDB evaluation mode instead.\r\n" +set warning "warning: Target does not support breakpoint condition evaluation.\r\nUsing host evaluation mode instead.\r\n" gdb_test_multiple $test_target $test_target { -re "$warning$gdb_prompt $" { -- 1.7.7.4 --G4iJoqBmSsgzjUCe--