From: Greg Watson <g.watson@computer.org>
To: "gdb@sourceware.cygnus.com" <gdb@sourceware.cygnus.com>
Subject: Re: Library interface to GDB
Date: Thu, 27 May 1999 21:52:00 -0000 [thread overview]
Message-ID: <374E218C.2075EF62@computer.org> (raw)
In-Reply-To: <863e0i9key.fsf@localhost.uni-trier.de>
Dave, Martin,
I too have been doing some work in this area that may be of interest. I've
developed a client/server debugger API using a combination of SunRPC and
Berkeley sockets that I guess falls somewhere between the CORBA/libgdb ideas
you've been discussing. My API is designed to interface directly with a UI/GUI
and is independent of the back-end debugger. Of course, I've also had to resort
to building a gdb command/response parser like the libdryad one. I've long
thought that it would be great to have a library interface to gdb commands, but
run into the same problems with libgdb as you've done. The architecure you
suggest below would fit extremely well into my project, so I'd be happy to be
involved in this as well.
Regards,
Greg Watson
Research Fellow
Monash University, Melbourne, Australia
Martin Baulig wrote:
> Dave Camp <campd@oit.edu> writes:
>
> > And Martin - perhaps we can discuss working together on a debugger -
> > taking some stuff from ggdb (for example, I like parts of the idl) and
> > putting in Dryad, or whatever. No sense in us working on redundant
> > projects. Email me and we'll discuss it.
>
> Yes, sure. And my GDB library idea is not really a "redundant project",
> it should be a very low-level interface to gdb which basically means to
> put gdb into a library, export all important functions and add some
> wrappers to things where gdb outputs text for instance.
>
> If I understood your implementation correctly, your CORBA interface will
> talk to libdryad which handles the interaction with the debugger but is
> independent from any special debugger. This is a very good idea since it
> gives people the chance to use dryad with a different debugger than gdb
> as well.
>
> I just want to insert an additional "layer of abstraction" - a low-level
> interface to gdb which libdry will use so we'll have something like
>
> application (ie. dryad) -> -> libgdb (for gdb)
>
> dryad CORBA -> libdryad
>
> other application -> -> libfoo (for bar)
>
> Of cause we can discuss this, we really should work together on this project.
>
> --
> Martin Baulig - martin@home-of-linux.org - http://www.home-of-linux.org
next prev parent reply other threads:[~1999-05-27 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-27 14:13 Martin Baulig
1999-05-27 23:03 ` Andrew Cagney
[not found] ` <87ogj6uqq1.fsf@cygnus.com>
[not found] ` <w53pv3mnoor.fsf@mystra.davec.dhs.org>
[not found] ` <863e0i9key.fsf@localhost.uni-trier.de>
1999-05-27 21:52 ` Greg Watson [this message]
1999-06-01 1:13 ` Magdalena Sujecka
1999-06-07 17:13 ` Stan Shebs
1999-06-07 17:42 ` Brendan Simon
1999-06-07 17:49 ` Stan Shebs
[not found] <199905272336.QAA03287@hpcll563.cup.hp.com>
1999-05-27 18:57 ` Brendan Simon
[not found] <199906082353.QAA23739@alabama.wrs.com>
1999-06-10 17:00 ` J.T. Conklin
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=374E218C.2075EF62@computer.org \
--to=g.watson@computer.org \
--cc=gdb@sourceware.cygnus.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