From: Kevin Pouget <kevin.pouget@gmail.com>
To: Grigory Tolstolytkin <gtolstolytkin@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Extending GDB to provide console over telnet
Date: Thu, 29 Sep 2011 12:17:00 -0000 [thread overview]
Message-ID: <CAPftXULNQOCd1zOVyRsX4kSEL6f2qqLUQ8fasXUqJUmy-nqkig@mail.gmail.com> (raw)
In-Reply-To: <4E845D53.9090102@gmail.com>
On Thu, Sep 29, 2011 at 1:58 PM, Grigory Tolstolytkin
<gtolstolytkin@gmail.com> wrote:
> Hi,
>
> I'm working on extending gdb functionality and would like to start a
> discussion since it might be useful for other people too.
>
> The idea is to provide users an ability to remotely connect to gdb and
> perform usual debugging interaction while it is already started in Eclipse
> environment via MI interface.
> This allows starting debug locally in Eclipse with connected target
> hardware, for example, and then pass debugging control to a remote user at
> some point.
>
> Preliminary design is as following:
> 1. gdb is started on a local host either with Eclipse (through MI) or in the
> shell.
> 2. Remote users will connect to gdb using telnet via TCP.
> Additional commands need to be introduced to start corresponding TCP
> service. Namely, "start-telnet-service [port]", "stop-telnet-service". TCP
> port can be specified explicitly or hardcoded one (default) will be used.
> 3. Remote users will used standard gdb console command syntax.
> 4. It seems reasonable to allow many users to connect to one instance of gdb
> (Thus having individual internal interpreter for each one).
> 5. Debugging process under Eclipse usually generates a lot of information in
> gdb output. The key idea is to separate MI input/output from the remote user
> consoles.
> Such debugging process when two or more users are involved into
> controlling gdb might be a bit confusing. For example if users are both
> setting breakpoints their numbers will differ from what users expect and so
> on. But this is not a usual scenario to simultaneously debug the
> application. So users should know what they're doing in such a case. Anyway,
> such operations must not break gdb internals and lead to unpredicted
> results.
>
> Any suggestions, opinions and discussions are highly welcome. I'm also
> already looking into implementation design and will provide details in
> future mails.
>
> Regards,
> Grigory
Hello,
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?
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.
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?)
Thanks for bringing up the idea,
Kevin
next prev parent reply other threads:[~2011-09-29 12:17 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 [this message]
2011-09-29 12:42 ` Grigory Tolstolytkin
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=CAPftXULNQOCd1zOVyRsX4kSEL6f2qqLUQ8fasXUqJUmy-nqkig@mail.gmail.com \
--to=kevin.pouget@gmail.com \
--cc=gdb@sourceware.org \
--cc=gtolstolytkin@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