From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21245 invoked by alias); 20 Jun 2013 16:20:35 -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 21235 invoked by uid 89); 20 Jun 2013 16:20:35 -0000 X-Spam-SWARE-Status: No, score=-7.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 20 Jun 2013 16:20:32 +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 r5KGJojL020681 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 Jun 2013 12:19:50 -0400 Received: from host2.jankratochvil.net (ovpn-116-40.ams2.redhat.com [10.36.116.40]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r5KGJjBv015611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 20 Jun 2013 12:19:48 -0400 Date: Thu, 20 Jun 2013 16:45:00 -0000 From: Jan Kratochvil To: "Metzger, Markus T" Cc: Joel Brobecker , "gdb-patches@sourceware.org" Subject: Re: [patch] Fix cleanup in finish_command Message-ID: <20130620161945.GA16142@host2.jankratochvil.net> References: <20130619211444.GA29379@host2.jankratochvil.net> <20130620143118.GA11929@host2.jankratochvil.net> <20130620151806.GD4724@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2013-06/txt/msg00547.txt.bz2 On Thu, 20 Jun 2013 17:26:56 +0200, Metzger, Markus T wrote: > Can you point me to a specific test where this happens? Each time with: gdb.btrace/tailcall.exp Build gdb with -lmcheck just to be sure. > Is there some indication in gdb.log? No. I get one FAIL but I expect it is due to buggy Nehalem: next^M 0x00000000004005d5 in main () at gdb/testsuite/gdb.btrace/x86-tailcall.c:37^M 37 answer = foo ();^M (gdb) FAIL: gdb.btrace/tailcall.exp: step, 1.5 > Are you using remote or native configuration? Native, just: ulimit -c unlimited; runtest gdb.btrace/tailcall.exp Pedro already gave an advice how to fix it properly if you take over this bug. Unrelated: There is testcase FAILing randomly, reproducible with "read1.so" from: http://sourceware.org/bugzilla/show_bug.cgi?id=12649 Running ./gdb.btrace/exception.exp ... FAIL: gdb.btrace/exception.exp: exception - flat (timeout) Thanks, Jan