From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19348 invoked by alias); 6 Feb 2012 19:38:14 -0000 Received: (qmail 19330 invoked by uid 22791); 6 Feb 2012 19:38:13 -0000 X-SWARE-Spam-Status: No, hits=-7.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 06 Feb 2012 19:37:59 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q16Jbt5r014674 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Feb 2012 14:37:55 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q16JbtSI006378; Mon, 6 Feb 2012 14:37:55 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id q16Jbqpg009607; Mon, 6 Feb 2012 14:37:53 -0500 From: Tom Tromey To: "Philippe Waroquiers" Cc: "Stan Shebs" , Subject: Re: (ping) Re: RFA: remote.c : allow long monitor cmds + allow user to C-c References: <1327265676.23561.25.camel@soleil> <4F1D5335.3090705@redhat.com> <1327350423.2215.6.camel@soleil> <1328220784.7612.5.camel@soleil> <4F2C4350.6030000@earthlink.net> Date: Mon, 06 Feb 2012 19:38:00 -0000 In-Reply-To: (Philippe Waroquiers's message of "Fri, 3 Feb 2012 23:39:33 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-02/txt/msg00062.txt.bz2 >>>>> "Philippe" == Philippe Waroquiers 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