Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Grigory Tolstolytkin <gtolstolytkin@gmail.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Extending GDB to provide console over telnet
Date: Thu, 29 Sep 2011 12:42:00 -0000	[thread overview]
Message-ID: <4E8467B1.60009@gmail.com> (raw)
In-Reply-To: <CAPftXULNQOCd1zOVyRsX4kSEL6f2qqLUQ8fasXUqJUmy-nqkig@mail.gmail.com>

Hi,

On 09/29/2011 04:16 PM, Kevin Pouget wrote:
> the idea sounds interesting, there is just one point I'm not sure to
> understand exactly in your email: which interface do you want to
> provide to the remote user: command-line (CLI) or MI?
>
It's CLI. I think it is more user-friendly rather than MI.
> from my point of view, the CLI would be very convenient, it would
> allow the use of Eclipse to navigate the source code (instead of
> where/list/up/down), and on the other side control the execution and
> everything else from the CLI, which is just very powerful when you
> know how to use it.
Exactly, it's one of the points.
> Actually, the best situation would be the other way around, control
> GDB 'directly' so that ReadLine history/completion is also available!
> (I don't thing it would work over the network, would it?)
As I know readline doesn't work well with sockets, but tools like rlwrap 
over telnet can be used. It's transparent to user and brings part of 
readline features like history, line editing, etc. Though gdb 
auto-completion is still a question.

> Thanks for bringing up the idea,
>
> Kevin
Regards,
Grigory


  reply	other threads:[~2011-09-29 12:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29 11:58 Grigory Tolstolytkin
2011-09-29 12:17 ` Kevin Pouget
2011-09-29 12:42   ` Grigory Tolstolytkin [this message]
2011-09-29 12:47 ` Matt Rice
2011-09-30 19:27 ` 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=4E8467B1.60009@gmail.com \
    --to=gtolstolytkin@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=kevin.pouget@gmail.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