Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sterling Augustine <saugustine@google.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [Patch] Mechanism for board files to set default remotetimeout
Date: Fri, 31 May 2013 22:49:00 -0000	[thread overview]
Message-ID: <CAEG7qUzff_JnpDReNcj4z=p+=VSZTwQMJeJOEcNvMfZJViN_Eg@mail.gmail.com> (raw)
In-Reply-To: <CAEG7qUxVaxn_J7G1jhUZFryK6ekoxaYZoLfGR8+Ke5y_m0HSgA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

On Fri, May 31, 2013 at 1:57 PM, Sterling Augustine
<saugustine@google.com> wrote:
> On Fri, May 31, 2013 at 3:13 AM, Pedro Alves <palves@redhat.com> 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.

How does this look? I considered using GDBFLAGS instead of
INTERNAL_GDBFLAGS, but lots of tests replace GDBFLAGS with their own
copy, preventing its use in many cases.

Sterling

2013-05-30  Sterling Augustine  <saugustine@google.com>

	* boards/remote-stdio-gdbserver.exp: Add code to customize remotetimeout
	value via INTERNAL_GDBFLAGS.

[-- Attachment #2: remotetimeout.patch --]
[-- Type: application/octet-stream, Size: 1135 bytes --]

Index: lib/gdb.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/lib/gdb.exp,v
retrieving revision 1.231
diff -u -r1.231 gdb.exp
--- lib/gdb.exp	6 May 2013 22:11:15 -0000	1.231
+++ lib/gdb.exp	31 May 2013 22:47:03 -0000
@@ -1403,6 +1403,7 @@
     global gdb_prompt
     global timeout
     global gdb_spawn_id;
+    global gdb_remotetimeout
 
     gdb_stop_suppressing_tests;
 
Index: boards/remote-stdio-gdbserver.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/boards/remote-stdio-gdbserver.exp,v
retrieving revision 1.1
diff -u -r1.1 remote-stdio-gdbserver.exp
--- boards/remote-stdio-gdbserver.exp	21 May 2013 17:58:46 -0000	1.1
+++ boards/remote-stdio-gdbserver.exp	31 May 2013 22:47:03 -0000
@@ -26,6 +26,13 @@
 
 load_board_description "native-stdio-gdbserver"
 
+global INTERNAL_GDBFLAGS
+if [info exists REMOTE_TIMEOUT] {
+    append INTERNAL_GDBFLAGS " -l $REMOTE_TIMEOUT"
+} else {
+    append INTERNAL_GDBFLAGS " -l 10"
+}
+
 set_board_info rsh_prog /usr/bin/ssh
 set_board_info rcp_prog /usr/bin/scp
 

  reply	other threads:[~2013-05-31 22:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 23:42 Sterling Augustine
2013-05-31 10:13 ` Pedro Alves
2013-05-31 20:57   ` Sterling Augustine
2013-05-31 22:49     ` Sterling Augustine [this message]
2013-06-03 11:31       ` Pedro Alves
2013-06-03 10:52     ` Pedro Alves
2013-06-03 11:09       ` Pedro Alves

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='CAEG7qUzff_JnpDReNcj4z=p+=VSZTwQMJeJOEcNvMfZJViN_Eg@mail.gmail.com' \
    --to=saugustine@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    /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