From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1351 invoked by alias); 31 May 2013 20:57:43 -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 1342 invoked by uid 89); 31 May 2013 20:57:43 -0000 X-Spam-SWARE-Status: No, score=-4.4 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.1 Received: from mail-ea0-f170.google.com (HELO mail-ea0-f170.google.com) (209.85.215.170) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 31 May 2013 20:57:42 +0000 Received: by mail-ea0-f170.google.com with SMTP id f15so2153761eak.1 for ; Fri, 31 May 2013 13:57:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=vztxi1ZqzFMfNCK1hy9eWvinN4QS6Z/oxoeigmTIPkU=; b=WCey9VtYVt0G271FNy8smV9IOP7enQbJIwJk+9qLvCsf8cY+jCeZE5uk7L/qgbfri1 sQOxWQO6FjH5R69mH6YwiPGxtHGD+WJDp858rGi8evucavVJdxYm3PewG0WGhAbcrogt 4aZZB9aP+7SgWLaFdrdJVzf5UC8AD5xG1o7fl2Abm9GChJOP1n+oRErUJp5t2uZnerXu EE71G7oVFGGueF/lnVHqkRorPbOIePX0KwfNFUCVQPws6K+u0MBNokTAGlxdzr7uoWP+ HAylGCBfVd9DD4apFFWOkEgvTQZGB+Uu25G4V1++B8JtJF/AI9ltE+15Q9eq48zBDdY4 n7BA== MIME-Version: 1.0 X-Received: by 10.15.111.202 with SMTP id cj50mr14713850eeb.140.1370033860295; Fri, 31 May 2013 13:57:40 -0700 (PDT) Received: by 10.223.87.193 with HTTP; Fri, 31 May 2013 13:57:40 -0700 (PDT) In-Reply-To: <51A877BD.4020804@redhat.com> References: <51A877BD.4020804@redhat.com> Date: Fri, 31 May 2013 20:57:00 -0000 Message-ID: Subject: Re: [Patch] Mechanism for board files to set default remotetimeout From: Sterling Augustine To: Pedro Alves Cc: gdb-patches Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkU8HGFWumogyo1oWcMjCq6cW4phO6SsgHRxPR8J0DQKdR4mnH58VUuwedGAMrH71KqOTbGgeP10tfFV1LNMygPoSQkisHFdMfPpjuJhKcdQB1ZHCcnBPUz7M/1TiiBPFBBCCz7tAndqvVMs4l3lBXo9YyJJaZdrol/GSYzAtewqhh2gVsQ8JDzzRjQW2wnFZIAIhgMbE9Mmmg2wuaj6Q+Z3I9cbw== X-SW-Source: 2013-05/txt/msg01119.txt.bz2 On Fri, May 31, 2013 at 3:13 AM, Pedro Alves wrote: > 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. I'll switch to this. >> 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? I meant to distinguish between the communication that happens between the user and gdb, and the communication that happens between gdb and gdbserver. Not very well, apparently. > > 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. Since I'm switching to the other mechanism, I guess I won't worry about this. I will however, separately submit a patch to the "set remotetimeout" command's documentation, mentioning that there is a command line option which does the same thing. Would have saved me a bit of trouble. > > -- > Pedro Alves >