This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: (ping) Re: RFA: remote.c : allow long monitor cmds + allow user to C-c
- From: "Philippe Waroquiers" <philippe dot waroquiers at skynet dot be>
- To: "Stan Shebs" <stanshebs at earthlink dot net>, <gdb-patches at sourceware dot org>
- Date: Fri, 3 Feb 2012 23:39:33 +0100
- 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> <m38vkxhib1.fsf@redhat.com> <1328220784.7612.5.camel@soleil> <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