Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org, toolchain-devel@blackfin.uclinux.org,
	Jie Zhang <jie.zhang@analog.com>,
	Joel Brobecker <brobecker@adacore.com>
Subject: Re: [toolchain-devel] [PATCH v2] gdb: tests: set remotetimeout to gdb_load_timeout for remote targets
Date: Thu, 30 Jun 2011 13:48:00 -0000	[thread overview]
Message-ID: <201106301447.53566.pedro@codesourcery.com> (raw)
In-Reply-To: <BANLkTimsaieDJdaazKOt0ZfZ=zQFB=rguA@mail.gmail.com>

On Thursday 30 June 2011 14:30:18, Mike Frysinger wrote:
> On Thu, Jun 30, 2011 at 04:58, Pedro Alves wrote:
> > On Wednesday 29 June 2011 17:25:27, Joel Brobecker wrote:
> >> > +    send_gdb "show remotetimeout\n"
> >> > +    gdb_expect {
> >>
> >> Can you use gdb_test_multiple instead?
> >
> > UUIC, that would add something like "PASS: show remotetimeout"
> > to every test.  Is that wanted?  I 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.

Ah, yes, you're right.  Thanks.

> ...
> (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
> 

-- 
Pedro Alves


  reply	other threads:[~2011-06-30 13:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-05 21:34 [PATCH] gdb: tests/monitor: " Mike Frysinger
2011-06-18 22:31 ` Mike Frysinger
2011-06-19 19:04 ` [PATCH v2] gdb: tests: " Mike Frysinger
2011-06-29 16:25   ` Joel Brobecker
2011-06-29 17:29     ` Jie Zhang
2011-06-30  8:59     ` Pedro Alves
2011-06-30 13:30       ` [toolchain-devel] " Mike Frysinger
2011-06-30 13:48         ` Pedro Alves [this message]
2011-06-29 23:25   ` [PATCH v3] " Mike Frysinger
2011-06-30 22:54     ` Joel Brobecker
2011-07-01  0:19       ` Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201106301447.53566.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jie.zhang@analog.com \
    --cc=toolchain-devel@blackfin.uclinux.org \
    --cc=vapier@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox