From: Joel Brobecker <brobecker@gnat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: a2782@dis.ulpgc.es, gdb@sources.redhat.com
Subject: Re: libgdb
Date: Fri, 22 Nov 2002 15:03:00 -0000 [thread overview]
Message-ID: <20021122230349.GO1259@gnat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0211221447360.1555-100000@valrhona.uglyboxes.com>
> 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
next prev parent reply other threads:[~2002-11-22 23:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 14:26 libgdb a2782
2002-11-22 14:52 ` libgdb Keith Seitz
2002-11-22 15:03 ` Joel Brobecker [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-02 16:45 libgdb Matthew Hall
2007-11-02 16:58 ` libgdb Daniel Jacobowitz
2007-11-02 20:30 ` libgdb Stan Shebs
2003-07-01 1:20 Frame handling Jafa
2003-07-01 3:42 ` Daniel Jacobowitz
[not found] ` <redirect-6800274@silicondust.com>
2003-07-01 5:13 ` Jafa
2003-07-01 12:58 ` Andrew Cagney
2003-07-01 14:09 ` Daniel Jacobowitz
[not found] ` <redirect-6810110@silicondust.com>
2003-07-01 17:00 ` Jafa
2003-07-02 7:13 ` libgdb jacques
2003-04-16 19:59 gdb's communication to a process/libgdb? Smita
2003-04-16 22:07 ` libgdb Smita
2003-04-17 1:44 ` libgdb Elena Zannoni
2003-04-17 2:06 ` libgdb Smita
2003-04-17 12:57 ` libgdb Elena Zannoni
2002-10-23 22:46 libgdb Satya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021122230349.GO1259@gnat.com \
--to=brobecker@gnat.com \
--cc=a2782@dis.ulpgc.es \
--cc=gdb@sources.redhat.com \
--cc=keiths@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).