From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6990 invoked by alias); 25 Apr 2003 02:36:13 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6983 invoked from network); 25 Apr 2003 02:36:12 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 25 Apr 2003 02:36:12 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 147532B2F; Thu, 24 Apr 2003 22:36:10 -0400 (EDT) Message-ID: <3EA89F19.10207@redhat.com> Date: Fri, 25 Apr 2003 02:36:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bob Rossi Cc: gdb@sources.redhat.com Subject: Re: gdb/mi or annotations detection References: <20030423111030.GA14799@white> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-04/txt/msg00310.txt.bz2 > Hi, > > How is the front end supposed to detect whether or not it should use > annotations or GDB/MI? I think there needs to be a way of doing this > besides starting it once for detection/failure for MI, and then starting > it again for annotations. > > Also, what about different versions of MI. As it progresses different > versions will have different functionality. How will the front end know > what functionality each version has? > > ex. > In the first release of MI there might not be the > -symbol-info-linetable command. So, the front end will have to give > commands 'info line' over and over. Then, when this command becomes > available in the next release, the front end can start using it > instead. > > The front end can not do a 'gdb --version' because usually there are > gdb's installed that are cvs snapshots ( debian ). > > Does anyone have any ideas? You can start gdb with -i=miN for a specific version, but that doesn't handle your case - you want to know the most up-to-date version in a running GDB. You'll also need to watch out for GDB's cut mid-branch. The version is only rolled when formal gdb releases are made. Andrew