From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18224 invoked by alias); 22 Nov 2002 23:03:55 -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 18216 invoked from network); 22 Nov 2002 23:03:53 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sources.redhat.com with SMTP; 22 Nov 2002 23:03:53 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 397B3D2CE5; Fri, 22 Nov 2002 15:03:49 -0800 (PST) Date: Fri, 22 Nov 2002 15:03:00 -0000 From: Joel Brobecker To: Keith Seitz Cc: a2782@dis.ulpgc.es, gdb@sources.redhat.com Subject: Re: libgdb Message-ID: <20021122230349.GO1259@gnat.com> References: <200211222324.gAMNORl06049@siglo21.dis.ulpgc.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-SW-Source: 2002-11/txt/msg00333.txt.bz2 > 1) Invoke GDB and parse the command line (emacs does this) > 2) Invoke GDB's MI interpreter and write yourself an MI parser (Eclipse > and Apple's tools for MacOS X do this) > 3) Write your GUI using GDB's hooks and events (Insight does this) > > Obviously, #2 is the most desirably way to isolate yourselves from GDB > changes. Unfortunately, MI is still a work in progress. (Of course, I'm > still partial to #3 for speed.. ;-) One advantage of method #1 or #2, used by GVD, is that GDB is a separate process. This GDB process does not need to run on the same host as GVD. Even if I'm debugging on a distant machine, I can run GVD on my local machine, reducing tremendously the network traffic. Given that I live in the west coast, and that most machines I work on are located in NY and Paris, this is a definite plus. I think GVD uses method #1, but I would recommend method #2 as the output is most probably easier to parse. -- Joel