From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9752 invoked by alias); 30 Aug 2004 15:40:15 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 9730 invoked from network); 30 Aug 2004 15:40:14 -0000 Received: from unknown (HELO mclean.mail.mindspring.net) (207.69.200.57) by sourceware.org with SMTP; 30 Aug 2004 15:40:14 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by mclean.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1C1oGS-0006HU-00; Mon, 30 Aug 2004 11:40:12 -0400 Received: from mindspring.com (localhost [127.0.0.1]) by berman.michael-chastain.com (Postfix) with SMTP id 49E394B102; Mon, 30 Aug 2004 11:40:33 -0400 (EDT) Date: Mon, 30 Aug 2004 15:40:00 -0000 From: Michael Chastain To: cagney@gnu.org Subject: Re: Infinite loop in sigstep.exp Cc: gdb@sources.redhat.com Message-ID: <41334A6F.nailEET1NDWIK@mindspring.com> References: <4133186C.nailO1B1RC12L@mindspring.com> <413333F4.5060304@gnu.org> In-Reply-To: <413333F4.5060304@gnu.org> User-Agent: nail 10.8 6/28/04 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00429.txt.bz2 This change seems to do the job: - exp_continue + exp_continue -continue_timer "-continue_timer" means that exp_continue does not reset the timeout counter for "expect". So after the usual 120 seconds, gdb_test_multiple busts out with a normal looking timeout FAIL. I have to check that -continue_timer works with the vintage 1998 "expect" in sourceware. ac> A [k]failing pattern for: ac> ac> "Breakpoint .*$gdb_prompt " ac> ac> would also help. Yes, it would. It would give a nice specific result, but just for this one case. If you want to submit a patch for that, go for it. I'm gonna experiment some more with "-continue_timer" which ought to break all cases of infinite loops.