From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14730 invoked by alias); 31 May 2013 10:13:23 -0000 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 Received: (qmail 14720 invoked by uid 89); 31 May 2013 10:13:23 -0000 X-Spam-SWARE-Status: No, score=-8.1 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 31 May 2013 10:13:22 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r4VADJV0006390 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 31 May 2013 06:13:19 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r4VADItS006145; Fri, 31 May 2013 06:13:19 -0400 Message-ID: <51A877BD.4020804@redhat.com> Date: Fri, 31 May 2013 10:13:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 MIME-Version: 1.0 To: Sterling Augustine CC: gdb-patches Subject: Re: [Patch] Mechanism for board files to set default remotetimeout References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-05/txt/msg01105.txt.bz2 On 05/31/2013 12:42 AM, Sterling Augustine wrote: > The enclosed simple patch adds and demonstrates a new mechanism for a > board file to declare a default remotetimeout. Took me a bit to realize this is about "set remotetimeout" in gdb, not the expect timeout. It wasn't that obvious from the description. :-) Is this really necessary? The board could just append "-l TIMEOUT" to the GDB command line invocation. Looks simpler, and doesn't depend on issuing an interactive GDB command. > It follows a similar mechanism as set height 0. > > This is useful if the board has high latency for internal gdb > commands, as remote-stdio-gdbserver.exp does. "high latency for internal gdb commands"? What does that mean? What are internal gdb commands? Testsuite knobs boards can tweak should be documented somewhere. Looks like under "Testsuite Configuration" in the gdbint manual might be a good place? Would be great if it was minimally documented in the .exp itself too. -- Pedro Alves