From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11471 invoked by alias); 22 Nov 2002 22:52:25 -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 11464 invoked from network); 22 Nov 2002 22:52:24 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 22 Nov 2002 22:52:24 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id gAMMSJP30135 for ; Fri, 22 Nov 2002 17:28:19 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id gAMMqOD21368; Fri, 22 Nov 2002 17:52:24 -0500 Received: from valrhona.uglyboxes.com (IDENT:ljSH0SchjwOLZTtlrTzJ1x1p22at2Twd@vpn50-10.rdu.redhat.com [172.16.50.10]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id gAMMqNw01750; Fri, 22 Nov 2002 17:52:23 -0500 Date: Fri, 22 Nov 2002 14:52:00 -0000 From: Keith Seitz X-X-Sender: keiths@valrhona.uglyboxes.com To: a2782@dis.ulpgc.es cc: gdb@sources.redhat.com Subject: Re: libgdb In-Reply-To: <200211222324.gAMNORl06049@siglo21.dis.ulpgc.es> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-11/txt/msg00332.txt.bz2 On Fri, 22 Nov 2002 a2782@dis.ulpgc.es wrote: > I am involved in a project of making a educational graphic interface > and we are thinking about putting it over GDB. My question is: Has > anybody worked with libgdb? My first approximation is invoking gdb as > Emacs does, but using libgdb. I hope someone has worked with libgdb and > can help and advise me. Sadly, libgdb is a pipedream, and still quite a ways off (but it's getting closer almost every day). There are three ways to commonly interface some sort of GUI application top of GDB: 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.. ;-) Keith