From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11558 invoked by alias); 8 Feb 2002 16:28:50 -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 11511 invoked from network); 8 Feb 2002 16:28:48 -0000 Received: from unknown (HELO fw-cam.cambridge.arm.com) (193.131.176.3) by sources.redhat.com with SMTP; 8 Feb 2002 16:28:48 -0000 Received: by fw-cam.cambridge.arm.com; id QAA24934; Fri, 8 Feb 2002 16:28:46 GMT Received: from unknown(172.16.1.2) by fw-cam.cambridge.arm.com via smap (V5.5) id xma024600; Fri, 8 Feb 02 16:28:26 GMT Received: from cam-mail2.cambridge.arm.com (localhost [127.0.0.1]) by cam-admin0.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id QAA18273 for ; Fri, 8 Feb 2002 16:28:26 GMT Received: from sun18.cambridge.arm.com (sun18.cambridge.arm.com [172.16.2.18]) by cam-mail2.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id QAA04564; Fri, 8 Feb 2002 16:28:25 GMT Message-Id: <200202081628.QAA04564@cam-mail2.cambridge.arm.com> X-Mailer: exmh version 2.0.2 2/24/98 To: gdb@sources.redhat.com cc: Richard.Earnshaw@arm.com Reply-To: Richard.Earnshaw@arm.com Organization: ARM Ltd. X-Telephone: +44 1223 400569 (direct+voicemail), +44 1223 400400 (switchbd) X-Fax: +44 1223 400410 X-Address: ARM Ltd., 110 Fulbourn Road, Cherry Hinton, Cambridge CB1 9NJ. X-Url: http://www.arm.com/ Subject: testsuite problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Feb 2002 08:28:00 -0000 From: Richard Earnshaw X-SW-Source: 2002-02/txt/msg00138.txt.bz2 I'm currently seeing the following when running the testsuite. Running /nfs/sun18/work/rearnsha/gnusrc/src/gdb/src/gdb/testsuite/gdb.base/ corefile.exp ... failed to get controlling terminal using TIOCSCTTYparent: sync byte write: broken pipe However, it only occurs if I'm running the whole suite. If I just run corefile.exp it completes ok. I seem to remember something like this once before (on another testsuite); IIRC it occurs when a connection to a child isn't shut down cleanly after a test (normally because the test failed in some way); the controlling pty isn't released cleanly and we then eventually run out of ptys. Could this be the problem here? -- certainly I'm seeing rather a large number of failures at the moment, since I'm in the middle of trying to raise the ARM code to multi-arch 1. R.