From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20079 invoked by alias); 26 Feb 2013 19:00:48 -0000 Received: (qmail 20057 invoked by uid 22791); 26 Feb 2013 19:00:45 -0000 X-SWARE-Spam-Status: No, hits=-6.7 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_SPAMHAUS_DROP,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS 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; Tue, 26 Feb 2013 19:00: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 r1QJ0aq8016977 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 26 Feb 2013 14:00:36 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r1QJ0VDY014638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 26 Feb 2013 14:00:33 -0500 From: Tom Tromey To: Yao Qi Cc: GDB Development Subject: Re: RFC - changes to the test suite References: <87fw0ta4jk.fsf@fleche.redhat.com> <51231E07.3010100@codesourcery.com> Date: Tue, 26 Feb 2013 19:00:00 -0000 In-Reply-To: <51231E07.3010100@codesourcery.com> (Yao Qi's message of "Tue, 19 Feb 2013 14:39:03 +0800") Message-ID: <87621e3nox.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.92 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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: 2013-02/txt/msg00092.txt.bz2 Tom> So, the first question is -- does anybody care strongly about where the Tom> files end up? And, if you do care, why do you care? Yao> When running testsuite with boardfile native-gdbserver.exp, does Yao> GDBserver need to know the updated location of files? or do we plan to Yao> spawn GDBserver in "./outputs/gdb.DIR/FILE" directory? I will test it and find out. Tom> I also added an "inotify" mode to the tests so you can easily see which Tom> tests write files outside of their specified directory. There are still Tom> a few remaining, I ran out of steam dotting every "i". Yao> What is the motivation of adding "inotify" mode? to monitor the Yao> progress of a given test, or something else? It is just for debugging the code to ensure that tests don't write outside of the allowed directories. It isn't perfect, but it helped me find some bugs, and I thought it would be handy to keep around. Tom