This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] New test for set backtrace related functionality

From: Andrew Cagney <cagney at gnu dot org>
To: pgilliam at us dot ibm dot com
Cc: Michael Chastain <mec dot gnu at mindspring dot com>, gdb-patches at sources dot redhat dot com
Date: Wed, 17 Nov 2004 17:01:18 -0500
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>

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

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]