From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26720 invoked by alias); 8 Mar 2007 18:39:13 -0000 Received: (qmail 26709 invoked by uid 22791); 8 Mar 2007 18:39:12 -0000 X-Spam-Check-By: sourceware.org Received: from mtagate8.de.ibm.com (HELO mtagate8.de.ibm.com) (195.212.29.157) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 08 Mar 2007 18:39:04 +0000 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate8.de.ibm.com (8.13.8/8.13.8) with ESMTP id l28Id1P6133002 for ; Thu, 8 Mar 2007 18:39:01 GMT Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l28Id1I32240766 for ; Thu, 8 Mar 2007 19:39:01 +0100 Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l28Id1Pf029085 for ; Thu, 8 Mar 2007 19:39:01 +0100 Received: from tuxmaker.boeblingen.de.ibm.com (tuxmaker.boeblingen.de.ibm.com [9.152.85.9]) by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with SMTP id l28Id1ok029082 for ; Thu, 8 Mar 2007 19:39:01 +0100 Message-Id: <200703081839.l28Id1ok029082@d12av02.megacenter.de.ibm.com> Received: by tuxmaker.boeblingen.de.ibm.com (sSMTP sendmail emulation); Thu, 8 Mar 2007 19:39:00 +0100 Subject: [rfc] Increase match_max size for GDB testsuite? To: gdb-patches@sourceware.org Date: Thu, 08 Mar 2007 18:39:00 -0000 From: "Ulrich Weigand" X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-03/txt/msg00086.txt.bz2 Hello, I'm seeing (somewhat random) failures in callfuncs.exp on spu, which appear to be caused by the length of the "info all-registers" output on the platform. I'm no dejagnu/expect expert, but seems to me there is a buffer size that is being set to 20000 in lib/gdb.exp, and if any response from the inferior exceeds this size, it's not completly predictable what happens. Now, since we have 128 registers on the SPU, and each is printed using a union of 7 different types, the output of "info all-registers" is quite long, in the range of 50000 bytes. This exceeds the above limit, and sometimes causes the test case to fail with "ERROR: internal buffer is full." Note that I've seen the same problem in the past with checkpoint.exp on s390x-ibm-linux (when retrieving the list of 600 checkpoints), so it doesn't appear to be a spu-only issue. By simply increasing the "match_max" argument in default_gdb_init, those failures go away. I didn't notice any adverse effects either, so I'd like to make that change -- however, if anybody has a better solution to the problem, please let me know ... Bye, Ulrich Index: gdb/testsuite/lib/gdb.exp =================================================================== RCS file: /cvs/src/src/gdb/testsuite/lib/gdb.exp,v retrieving revision 1.78 diff -c -p -r1.78 gdb.exp *** gdb/testsuite/lib/gdb.exp 23 Jan 2007 17:11:55 -0000 1.78 --- gdb/testsuite/lib/gdb.exp 8 Mar 2007 18:12:31 -0000 *************** proc default_gdb_init { args } { *** 1952,1958 **** # Uh, this is lame. Really, really, really lame. But there's this *one* # testcase that will fail in random places if we don't increase this. ! match_max -d 20000 # We want to add the name of the TCL testcase to the PASS/FAIL messages. if { [llength $args] > 0 } { --- 1952,1958 ---- # Uh, this is lame. Really, really, really lame. But there's this *one* # testcase that will fail in random places if we don't increase this. ! match_max -d 100000 # We want to add the name of the TCL testcase to the PASS/FAIL messages. if { [llength $args] > 0 } { -- Dr. Ulrich Weigand GNU Toolchain for Linux on System z and Cell BE Ulrich.Weigand@de.ibm.com