From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1983 invoked by alias); 4 Jul 2011 10:09:38 -0000 Received: (qmail 1973 invoked by uid 22791); 4 Jul 2011 10:09:37 -0000 X-SWARE-Spam-Status: No, hits=-6.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,TW_BJ,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; Mon, 04 Jul 2011 10:09:07 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p64A95RE002135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 4 Jul 2011 06:09:05 -0400 Received: from localhost.localdomain (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p64A94Sk003480; Mon, 4 Jul 2011 06:09:04 -0400 From: Phil Muldoon To: Matt Rice Cc: gdb-patches@sourceware.org Subject: Re: [patch] gdb.python tests, fix up paths References: Reply-to: pmuldoon@redhat.com X-URL: http://www.redhat.com Date: Mon, 04 Jul 2011 10:29:00 -0000 In-Reply-To: (Matt Rice's message of "Sun, 3 Jul 2011 23:35:44 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes 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: 2011-07/txt/msg00084.txt.bz2 Matt Rice writes: > This fixes some issues with the paths, > i'm seeing these all as './gdb.python/' here. > > 2011-07-03 Matt Rice > > * gdb.python/python.exp: Update filename paths. > * gdb.python/py-symtab.exp: Ditto. > diff --git a/gdb/testsuite/gdb.python/py-symtab.exp b/gdb/testsuite/gdb.python/py-symtab.exp > index c52f5ef..ef35c5d 100644 > --- a/gdb/testsuite/gdb.python/py-symtab.exp > +++ b/gdb/testsuite/gdb.python/py-symtab.exp > @@ -54,13 +54,13 @@ gdb_py_test_silent_cmd "python sal = frame.find_sal()" "Get block" 0 > gdb_py_test_silent_cmd "python symtab = sal.symtab" "Get block" 0 > > # Test sal. > -gdb_test "python print sal.symtab" "gdb/testsuite/gdb.python/py-symbol.c.*" "Test symtab" > +gdb_test "python print sal.symtab" ".*gdb.python/py-symbol.c.*" "Test symtab" While this is okay, and right now reflects how we test, I am curious to see what paths your testsuite instance is seeing. Are you building in-tree or out-of-tree (not that it matters beyond curiosity, the tests should work regardless). Needs a testsuite/ChangeLog too. > In addition to these, I'm getting another error I haven't been able to > figure out. > the logs are pretty silent on the subject, here is the only useful > info i've found... > py-objfile-script-gdb.py consistently disappears after running the testsuite. I can't test this right now due to the binutils bug you reported. When that is resolved, I will take a look. Cheers Phil