From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13266 invoked by alias); 28 Jan 2005 15:34:24 -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 12309 invoked from network); 28 Jan 2005 15:33:45 -0000 Received: from unknown (HELO lakermmtao06.cox.net) (68.230.240.33) by sourceware.org with SMTP; 28 Jan 2005 15:33:45 -0000 Received: from white ([68.9.64.121]) by lakermmtao06.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20050128153345.QDJL7687.lakermmtao06.cox.net@white> for ; Fri, 28 Jan 2005 10:33:45 -0500 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1CuY81-0000p4-00 for ; Fri, 28 Jan 2005 10:33:45 -0500 Date: Fri, 28 Jan 2005 15:34:00 -0000 From: Bob Rossi To: gdb@sources.redhat.com Subject: Add GDB/MI syntax check to testsuite Message-ID: <20050128153345.GA2954@white> Mail-Followup-To: gdb@sources.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-SW-Source: 2005-01/txt/msg00154.txt.bz2 Hi, So, I've got a Tcl extension that can check the syntax of a GDB/MI Output Command. I've tested it on small examples, and it seems to work. The original goal of allowing the Tcl to walk the parse tree will not be done with the initial patch. That task requires a lot more thought (However, it is easy to pass this extension a string(MI Output command), and have it return if the MI output command is valid or invalid syntactically. The problem now is, trying to figure out how to build tcl into a shared object library(in the gdb tree of course). Then how to link that into expect. - Would this be OK to do? - Does anyone have any pointers on how to do this? If it's not OK to make tcl into a shared library (maybe some hosts can't do this?) than I'll have to figure out how to link the extension statically into tcl. I think creating a "static extension" is like creating a custom version of a tcl interpreter. So, creating a static extension and a normal extension might be very different. Thanks, Bob Rossi