From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2109 invoked by alias); 17 Nov 2004 22:01:54 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 1523 invoked from network); 17 Nov 2004 22:01:34 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 17 Nov 2004 22:01:34 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id iAHM1TBY014172 for ; Wed, 17 Nov 2004 17:01:29 -0500 Received: from localhost.redhat.com (to-dhcp51.toronto.redhat.com [172.16.14.151]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id iAHM1Tr28874; Wed, 17 Nov 2004 17:01:29 -0500 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 3103E129D8C; Wed, 17 Nov 2004 17:01:24 -0500 (EST) Message-ID: <419BCA2E.9060701@gnu.org> Date: Wed, 17 Nov 2004 22:01:00 -0000 From: Andrew Cagney User-Agent: Mozilla Thunderbird 0.8 (X11/20041020) MIME-Version: 1.0 To: pgilliam@us.ibm.com Cc: Michael Chastain , gdb-patches@sources.redhat.com Subject: Re: [patch] New test for set backtrace related functionality References: <200410141539.22560.pgilliam@us.ibm.com> <200410210955.15904.pgilliam@us.ibm.com> <41792E5A.nailCWS110OUT@mindspring.com> <200410220957.46790.pgilliam@us.ibm.com> <41798044.nailDG51QLXJD@mindspring.com> In-Reply-To: <41798044.nailDG51QLXJD@mindspring.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-11/txt/msg00362.txt.bz2 > Here's the tough problem. I'm getting a weird random timeout on the > "partial backtrace (using limit)" test. In a group of 12 > configurations, I saw 2 PASS and 12 FAIL/timeout. I suspect some ".*" > or "[^foo]*" that is too greedy and eating more than it should, leaving > the later bits of the expect_list out to dry. gdb_expect_list is > matching them one at a time so there is no backtracking if an early r.e. > mistakenly eats too much. Specifically, it might be a problem with the > definition of $leadin. Paul, were you able to reproduce this problem? Andrew