From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5091 invoked by alias); 29 Sep 2011 11:58:26 -0000 Received: (qmail 5082 invoked by uid 22791); 29 Sep 2011 11:58:25 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Received: from mail-iy0-f169.google.com (HELO mail-iy0-f169.google.com) (209.85.210.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Sep 2011 11:58:11 +0000 Received: by iaen33 with SMTP id n33so834412iae.0 for ; Thu, 29 Sep 2011 04:58:11 -0700 (PDT) Received: by 10.42.18.197 with SMTP id y5mr724690ica.54.1317297490971; Thu, 29 Sep 2011 04:58:10 -0700 (PDT) Received: from [137.202.140.179] (nat-rup.mentorg.com. [139.181.168.34]) by mx.google.com with ESMTPS id bk20sm2311823ibb.2.2011.09.29.04.58.08 (version=SSLv3 cipher=OTHER); Thu, 29 Sep 2011 04:58:09 -0700 (PDT) Message-ID: <4E845D53.9090102@gmail.com> Date: Thu, 29 Sep 2011 11:58:00 -0000 From: Grigory Tolstolytkin User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 MIME-Version: 1.0 To: gdb@sourceware.org Subject: Extending GDB to provide console over telnet Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/msg00128.txt.bz2 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