From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 87871 invoked by alias); 22 Nov 2019 12:44:14 -0000 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 Received: (qmail 87808 invoked by uid 89); 22 Nov 2019 12:44:14 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-12.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy= X-HELO: mx1.suse.de Received: from mx2.suse.de (HELO mx1.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 22 Nov 2019 12:44:12 +0000 Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 2EE5DAB91; Fri, 22 Nov 2019 12:44:10 +0000 (UTC) Subject: Re: [PATCHv2 4/4] gdb: Add new commands to list module variables and functions To: Andrew Burgess , gdb-patches References: <2572574a445f9f32b4cca9a6f767d8495f4503c1.1570101531.git.andrew.burgess@embecosm.com> From: Tom de Vries Message-ID: Date: Fri, 22 Nov 2019 12:44:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 MIME-Version: 1.0 In-Reply-To: <2572574a445f9f32b4cca9a6f767d8495f4503c1.1570101531.git.andrew.burgess@embecosm.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-11/txt/msg00700.txt.bz2 On 03-10-2019 13:29, Andrew Burgess wrote: > * gdb.fortran/info-modules.exp: Update expected results, and add > additional tests for 'info module functinos', and 'info module > variables'. > * gdb.fortran/info-types.exp: Update expected results. > * gdb.fortran/info-types.f90: Extend testcase with additional > module variables and functions. Hi, This test-case fails to compile for me: ... $ cd build/gdb; make check RUNTESTFLAGS="gdb.fortran/info-modules.exp" gdb compile failed, src/gdb/testsuite/gdb.fortran/info-types.f90:39:6: use mod2 1 Fatal Error: Can't open module file 'mod2.mod' for reading at (1): No such file or directory compilation terminated. === gdb Summary === # of untested testcases 1 ... Interestingly, if I first run: ... $ cd build/gdb; make check RUNTESTFLAGS="gdb.fortran/module.exp" Running src/gdb/testsuite/gdb.fortran/module.exp ... === gdb Summary === # of expected passes 27 ... which produces: ... $ ls -la build/gdb/testsuite/mod2.mod -rw-r--r-- 1 vries users 208 22 nov 13:35 build/gdb/testsuite/mod2.mod ... then the test-case passes: ... $ cd build/gdb; make check RUNTESTFLAGS="gdb.fortran/info-modules.exp" Running src/gdb/testsuite/gdb.fortran/info-modules.exp ... === gdb Summary === # of expected passes 12 ... Removing mod2.mod brings the failure back: ... $ rm -f build/gdb/testsuite/mod2.mod $ cd build/gdb; make check RUNTESTFLAGS="gdb.fortran/info-modules.exp" gdb compile failed, src/gdb/testsuite/gdb.fortran/info-types.f90:39:6: use mod2 1 Fatal Error: Can't open module file 'mod2.mod' for reading at (1): No such file or directory compilation terminated. === gdb Summary === # of untested testcases 1 ... So, I think that in a parallel test run this may succeed, but in a sequential testrun this should fail. Thanks, - Tom