From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 41346 invoked by alias); 13 Aug 2015 22:28:00 -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 41336 invoked by uid 89); 13 Aug 2015 22:27:59 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 13 Aug 2015 22:27:57 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id 25345344F75; Thu, 13 Aug 2015 22:27:56 +0000 (UTC) Received: from localhost (unused-10-15-17-51.yyz.redhat.com [10.15.17.51]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t7DMRtSu005143 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 13 Aug 2015 18:27:55 -0400 From: Sergio Durigan Junior To: Patrick Palka Cc: "gdb-patches\@sourceware.org" Subject: Re: Racy failures on gdb.base/gdbinit-history.exp (native-extended-gdbserver/-m64) References: <1433878062-23560-1-git-send-email-patrick@parcs.ath.cx> <1434466413-28892-1-git-send-email-patrick@parcs.ath.cx> <87mvym67i5.fsf_-_@redhat.com> X-URL: http://blog.sergiodj.net Date: Thu, 13 Aug 2015 22:28:00 -0000 In-Reply-To: (Patrick Palka's message of "Thu, 13 Aug 2015 11:18:07 -0400") Message-ID: <87zj1un7ro.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2015-08/txt/msg00373.txt.bz2 On Thursday, August 13 2015, Patrick Palka wrote: > On Thu, Jul 23, 2015 at 2:42 PM, Sergio Durigan Junior > wrote: >> On Tuesday, June 16 2015, Patrick Palka wrote: >> >>> We still do not handle "set history size unlimited" correctly. In >>> particular, after writing to the history file, we truncate the history >>> even if it is unlimited. >>> >>> This patch makes sure that we do not call history_truncate_file() if the >>> history is not stifled (i.e. if it's unlimited). This bug causes the >>> history file to be truncated to zero on exit when one has "set history >>> size unlimited" in their gdbinit file. Although this code exists in GDB >>> 7.8, the bug is masked by a pre-existing bug that's been only fixed in >>> GDB 7.9 (PR gdb/17820). >> >> Hey Patrick, >> >> Looking at the BuildBot logs today, I found that this new test is >> failing occasionally on native-extended-gdbserver testing. Take a look >> at the following build: >> >> >> >> You can see that gdb.base/gdbinit-history.exp failed: >> >> PASS -> FAIL: gdb.base/gdbinit-history.exp: truncation: appending: server show commands >> PASS -> FAIL: gdb.base/gdbinit-history.exp: truncation: creating: server show commands >> >> The gdb.log is here: >> >> >> >> I haven't really investigated to determine what's going on here, but let >> me know if you need any help with this. > > Hi Sergio, > > Have you seen these spurious FAILs pop up recently? I wonder if the > fixes to SIGTERM handling I made a few weeks ago may have fixed this > as well. Hey Patrick, Yeah, I still see those FAIL's from time to time: I may be wrong, but I noticed that the FAIL's happen only on the PPC buildslaves. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/