From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27482 invoked by alias); 8 Jul 2008 22:16:35 -0000 Received: (qmail 27470 invoked by uid 22791); 8 Jul 2008 22:16:35 -0000 X-Spam-Check-By: sourceware.org Received: from mailhost.u-strasbg.fr (HELO mailhost.u-strasbg.fr) (130.79.200.158) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 08 Jul 2008 22:16:15 +0000 Received: from baal.u-strasbg.fr (baal.u-strasbg.fr [IPv6:2001:660:2402::41]) by mailhost.u-strasbg.fr (8.14.2/jtpda-5.5pre1) with ESMTP id m68MG9ox069215 ; Wed, 9 Jul 2008 00:16:09 +0200 (CEST) Received: from mailserver.u-strasbg.fr (ms2.u-strasbg.fr [IPv6:2001:660:2402::142]) by baal.u-strasbg.fr (8.14.0/jtpda-5.5pre1) with ESMTP id m68MG9op035461 ; Wed, 9 Jul 2008 00:16:09 +0200 (CEST) Received: from d620muller ([130.79.244.152]) by mailserver.u-strasbg.fr (8.13.8/jtpda-5.5pre1) with ESMTP id m68MG1rj008692 ; Wed, 9 Jul 2008 00:16:09 +0200 (CEST) From: "Pierre Muller" To: "'Pedro Alves'" , References: <000901c8def8$137b1bf0$3a7153d0$@u-strasbg.fr> <200807060456.49298.pedro@codesourcery.com> In-Reply-To: <200807060456.49298.pedro@codesourcery.com> Subject: Spurius results for cygwin selftest.exp(was Re: [RFC] fix annoying completion bug on directories) Date: Tue, 08 Jul 2008 22:16:00 -0000 Message-ID: <000101c8e148$37967000$a6c35000$@u-strasbg.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Content-Language: en-us X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (mailhost.u-strasbg.fr [IPv6:2001:660:2402::158]); Wed, 09 Jul 2008 00:16:10 +0200 (CEST) X-Virus-Status: Clean 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: 2008-07/txt/msg00119.txt.bz2 > > I ran the testsuite on cygwin, and found one > > change, but in gdb.gdb/selftest. > > FAIL (timeout) xgdb is at prompt > > > > I suspect that this is due to a problem with the > > [New thread %s] output, that are now default. > > Because this output appears right after the gdb prompt, > > and thus the match with a gdb prompt exactly at the end > > is not found. > > In these cases, in addition to analising the log file, please > rerun the test to confirm it was spurious. Cygwin testing > is indeed flackier than linux. This is indeed a spurious FAIL that has to do with that third thread that start on cygwin right after the command prompt is printed out. Does anyone know why there is a third thread starting? Debugging threads under cygwin is quite difficult, you never really know where they are coming from... I am really surprised that now, by default, gdb will print debug message, while the inferior is running, without stopping it. For me, when gdb is started with the default options, gdb should only output text if it stops the debuggee, otherwise it becomes difficult for the average user to handle. But I understood that the [New thread... message was already the default on Linux targets.. > > Just do make check RUNTESTFLAGS="failingtest.exp" a couple of > times. If it's always failing now, it's a regression. If > the failure goes aways, then also retest with with the > patch unapplied. You should see the flackiness too. If > not, it may be a regression, but you'll have to judge from > the logs -- it may just be difficult to reproduce flackiness. I got it give PASS or FAIL several times, it's really a question of how much time there is in between the (gdb) prompt and the [New thread...] message. I could of of course update the selftest.exp test to also accept the "[New thread ...]" message, but I would like your opinions about this before, we could easily suppress these messages by setting print_thread_events to zero by default. Pierre Muller Pascal language support maintainer for GDB