This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [toolchain-devel] [PATCH v2] gdb: tests: set remotetimeout to gdb_load_timeout for remote targets


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]