Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch] MI telnet service
Date: Tue, 17 Jul 2012 17:53:00 -0000	[thread overview]
Message-ID: <ju48q9$8eg$1@dough.gmane.org> (raw)
In-Reply-To: <EB3B29AD43CA924DA27099BC8519237629DF36@EU-MBX-03.mgc.mentorg.com>

On 12.07.2012 15:20, Abid, Hafiz wrote:
> Hi,
> This patch provides implementation of telnet service. This is based on initial work by Grigory Tolstolytkin.(http://sourceware.org/ml/gdb-patches/2011-11/msg00466.html)
>
> This service can accept and execute CLI commands from the remote user. It can be started by  MI command "-start-telnet-service [port]". After the service is running, user can connect to the GDB via telnet and execute CLI commands in parallel with existing MI interface. This service can be stopped by another MI command "-stop-telnet-service". For these commands to work, GDB has to be configured with --enable-gdbmitel=yes.
>
> This service can be useful, for example, when GDB is running as a backend of an IDE. Testing infrastructure can run the tests by sending commands through socket. In case of an error, a user can debug the problem in the IDE.
>
> The test case that I added only checks that port is opened after the service is started. I am looking to improve it and would appreciate if the reviewers can help me with some ideas.
>
> How does it all look?

Hi Abid,

it seems to me that the essential part of this patch does not have much to do with MI proper, and therefore it should live outside of 'mi' 
subdirectory.

>        * mi/mi-cmds.c (mi_cmds): Add -start-telnet-service
>        and stop-telnet-service MI commands.
>        * mi/mi-cmds.h (mi_cmd_start_telnet_service): Add declaration.
>        (mi_cmd_stop_telnet_service): Add declaration.

These changes, well, all 8 lines, look OK.

>        * mi/mi-telnet.c: New file.

Beyond the suggestion that this code not be put under 'mi' directory, I have no say about the idea or implementation.

Thanks,
Volodya


  parent reply	other threads:[~2012-07-17 17:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12 11:21 Abid, Hafiz
2012-07-12 13:19 ` Gary Benson
2012-07-12 14:37   ` Abid, Hafiz
2012-07-12 15:08     ` Gary Benson
2012-07-15  8:13     ` Jan Kratochvil
2012-07-12 13:29 ` Eli Zaretskii
2012-07-12 14:45   ` Abid, Hafiz
2012-07-14 19:37     ` Marc Khouzam
2012-07-24 16:17       ` Abid, Hafiz
2012-07-24 19:06         ` Marc Khouzam
2012-07-24 20:15           ` Marc Khouzam
2012-07-17 17:53 ` Vladimir Prus [this message]
2012-07-25 13:02 ` Jan Kratochvil
2012-07-25 14:12   ` Marc Khouzam
2012-07-25 19:27     ` Jan Kratochvil
2012-07-26  0:02       ` Stan Shebs
2012-07-26 11:51         ` Jan Kratochvil
2012-08-03 11:36       ` Jan Kratochvil
2012-07-25 14:16   ` Abid, Hafiz
2012-07-25 19:29     ` Jan Kratochvil

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='ju48q9$8eg$1@dough.gmane.org' \
    --to=ghost@cs.msu.su \
    --cc=gdb-patches@sources.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