Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Philippe Waroquiers" <philippe.waroquiers@skynet.be>
To: "Stan Shebs" <stanshebs@earthlink.net>,	<gdb-patches@sourceware.org>
Subject: Re: (ping) Re: RFA: remote.c : allow long monitor cmds + allow user to C-c
Date: Fri, 03 Feb 2012 22:39:00 -0000	[thread overview]
Message-ID: <BAC975E707284D279495A90A2602BFD0@soleil> (raw)
In-Reply-To: <4F2C4350.6030000@earthlink.net>

> Looks reasonable to me, let's put it in.  I don't suppose there's any 
> easy way to make a testsuite test for it?

Thanks for the feedback, will commit.

Effectively, no easy way to have a testsuite test for that, as a remote command
taking a long time is needed for that.

A possible approach would be to write a test checking if a valgrind >= 3.7.0
is available (as Valgrind has a 'v.wait xxxx' milliseconds monitor command).
Not clear to me just this is worth the effort. However, the added bonus
would be to have in gdb one (or more) tests checking the connection
with the Valgrind gdbserver.

Currently, only the Valgrind test suite has tests testing the connection between its
gdbserver and gdb.

Philippe


  reply	other threads:[~2012-02-03 22:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23  9:42 Philippe Waroquiers
2012-01-23 12:43 ` Pedro Alves
2012-01-23 21:09   ` Philippe Waroquiers
2012-01-24  4:43     ` Sergio Durigan Junior
2012-01-24  4:52       ` Philippe Waroquiers
2012-02-02 22:13       ` (ping) " Philippe Waroquiers
2012-02-03 20:28         ` Stan Shebs
2012-02-03 22:39           ` Philippe Waroquiers [this message]
2012-02-06 19:38             ` Tom Tromey

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=BAC975E707284D279495A90A2602BFD0@soleil \
    --to=philippe.waroquiers@skynet.be \
    --cc=gdb-patches@sourceware.org \
    --cc=stanshebs@earthlink.net \
    /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