From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23219 invoked by alias); 1 Jan 2004 22:16:19 -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 23211 invoked from network); 1 Jan 2004 22:16:18 -0000 Received: from unknown (HELO maynard.mail.mindspring.net) (207.69.200.243) by sources.redhat.com with SMTP; 1 Jan 2004 22:16:18 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by maynard.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1AcB6Y-00038N-00; Thu, 01 Jan 2004 17:15:47 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id C2A754B35A; Thu, 1 Jan 2004 17:15:45 -0500 (EST) To: drow@mvista.com, mec.gnu@mindspring.com Subject: Re: C++ testsuite changes Cc: gdb@sources.redhat.com, kettenis@chello.nl Message-Id: <20040101221545.C2A754B35A@berman.michael-chastain.com> Date: Thu, 01 Jan 2004 22:16:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-01/txt/msg00017.txt.bz2 drow> Can you identify what expect feature was causing the problem? I'm drow> quite curious. I'm working on it. Something like this is happening: virtfunc.exp calls gdb_test_multiple gdb_test_multiple gets the "eof" case virtfunc.exp calls gdb_test_multiple with nearly the same pattern gdb_test_multiple gets the "eof" case virtfunc.exp calls gdb_test_multiple with nearly the same pattern gdb_test_multiple gets the "eof" case virtfunc.exp calls gdb_test_multiple with nearly the same pattern gdb_test_multiple gets the "eof" case virtfunc.exp calls gdb_test_multiple with a different pattern gdb_test_multiple recovers and gets normal output! I'll try futzing with the problem pattern and see if that makes the problem go away. drow> I suspect we need to do an expect update... Well, tcl 8.4.5 + expect 5.3.9 + dejagnu 1.4.3 works fine on hppa2.0w-hp-hpux11.11 (as well as i686-pc-linux-gnu of course). What would it take to do an expect update? In particular, what is the list of hosts that have to be tested with a new version of 'expect' in order to do an expect update? Michael C