From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25198 invoked by alias); 30 Jun 2011 13:30:54 -0000 Received: (qmail 25188 invoked by uid 22791); 30 Jun 2011 13:30:54 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-gy0-f169.google.com (HELO mail-gy0-f169.google.com) (209.85.160.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 30 Jun 2011 13:30:39 +0000 Received: by gyg13 with SMTP id 13so1095946gyg.0 for ; Thu, 30 Jun 2011 06:30:38 -0700 (PDT) Received: by 10.91.198.35 with SMTP id a35mr542474agq.68.1309440638089; Thu, 30 Jun 2011 06:30:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.90.92.18 with HTTP; Thu, 30 Jun 2011 06:30:18 -0700 (PDT) In-Reply-To: <201106300958.52442.pedro@codesourcery.com> References: <1307309678-10966-1-git-send-email-vapier@gentoo.org> <1308510312-5512-1-git-send-email-vapier@gentoo.org> <20110629162527.GC2407@adacore.com> <201106300958.52442.pedro@codesourcery.com> From: Mike Frysinger Date: Thu, 30 Jun 2011 13:30:00 -0000 Message-ID: Subject: Re: [toolchain-devel] [PATCH v2] gdb: tests: set remotetimeout to gdb_load_timeout for remote targets To: Pedro Alves Cc: gdb-patches@sourceware.org, toolchain-devel@blackfin.uclinux.org, Jie Zhang , Joel Brobecker Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes 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: 2011-06/txt/msg00490.txt.bz2 On Thu, Jun 30, 2011 at 04:58, Pedro Alves wrote: > On Wednesday 29 June 2011 17:25:27, Joel Brobecker wrote: >> > + =C2=A0 =C2=A0send_gdb "show remotetimeout\n" >> > + =C2=A0 =C2=A0gdb_expect { >> >> Can you use gdb_test_multiple instead? > > UUIC, that would add something like "PASS: show remotetimeout" > to every test. =C2=A0Is that wanted? =C2=A0I was under the impression that > was the reason we didn't use gdb_test_multiple for infrustructure > setup within gdb.exp. i think that's only if the expect code passed to it calls `pass`. when i ran it, i didnt see any "PASS: show remotetimeout" ... while, i did test with gdb-6.6, i dont think this func has changed. ... (gdb) target remote vapier:2000 Remote debugging using vapier:2000 0x20000000 in ?? () (gdb) show remotetimeout Timeout limit to wait for target to respond is 2. (gdb) set remotetimeout 1600 ... Transfer rate: 385771 bits/sec, 5067 bytes/write. (gdb) set remotetimeout 2 (gdb) set print sevenbit-strings ... -mike