From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13172 invoked by alias); 29 Sep 2011 12:17:15 -0000 Received: (qmail 12823 invoked by uid 22791); 29 Sep 2011 12:17:12 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-vw0-f41.google.com (HELO mail-vw0-f41.google.com) (209.85.212.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Sep 2011 12:16:57 +0000 Received: by vws16 with SMTP id 16so466558vws.0 for ; Thu, 29 Sep 2011 05:16:57 -0700 (PDT) Received: by 10.52.100.99 with SMTP id ex3mr10242927vdb.116.1317298617196; Thu, 29 Sep 2011 05:16:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.200.132 with HTTP; Thu, 29 Sep 2011 05:16:37 -0700 (PDT) In-Reply-To: <4E845D53.9090102@gmail.com> References: <4E845D53.9090102@gmail.com> From: Kevin Pouget Date: Thu, 29 Sep 2011 12:17:00 -0000 Message-ID: Subject: Re: Extending GDB to provide console over telnet To: Grigory Tolstolytkin Cc: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-09/txt/msg00129.txt.bz2 On Thu, Sep 29, 2011 at 1:58 PM, Grigory Tolstolytkin 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. > =A0 =A0Additional commands need to be introduced to start corresponding T= CP > 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 u= ser > consoles. > =A0 =A0Such 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. Anyw= ay, > 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