Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Philippe Waroquiers" <philippe.waroquiers@skynet.be>
Cc: "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: Mon, 06 Feb 2012 19:38:00 -0000	[thread overview]
Message-ID: <m34nv3oir3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <BAC975E707284D279495A90A2602BFD0@soleil> (Philippe Waroquiers's	message of "Fri, 3 Feb 2012 23:39:33 +0100")

>>>>> "Philippe" == Philippe Waroquiers <philippe.waroquiers@skynet.be> writes:

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

I think it would be worthwhile, if you are willing.

There is already one valgrind test in gdb, but it doesn't test the new
embedded gdbserver work.  See gdb/testsuite/gdb.base/valgrind-db-attach.exp

Tom


      reply	other threads:[~2012-02-06 19:38 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
2012-02-06 19:38             ` Tom Tromey [this message]

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=m34nv3oir3.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    --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