public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Matthew Hall <matthewwwhall@googlemail.com>
Cc: gdb@sourceware.org
Subject: Re: libgdb
Date: Fri, 02 Nov 2007 16:58:00 -0000	[thread overview]
Message-ID: <20071102165833.GA1052@caradoc.them.org> (raw)
In-Reply-To: <79b61a440711020945y21ac07ei825b9c3e7ee1cc39@mail.gmail.com>

On Fri, Nov 02, 2007 at 04:45:45PM +0000, Matthew Hall wrote:
> I've seen references to a libgdb project.
> Can anyone tell me if libgdb is still active?

No.

> Is it complete?

No.

> Is it used internally by gdb itself?

No clear answer to this.  There was a "libgdb interface"; some bits of
GDB use it, other bits do not.  It's all linked in together.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2007-11-02 16:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 16:45 libgdb Matthew Hall
2007-11-02 16:58 ` Daniel Jacobowitz [this message]
2007-11-02 20:30 ` libgdb Stan Shebs
  -- strict thread matches above, loose matches on Subject: below --
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-11-22 14:26 libgdb a2782
2002-11-22 14:52 ` libgdb Keith Seitz
2002-11-22 15:03   ` libgdb Joel Brobecker
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=20071102165833.GA1052@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=matthewwwhall@googlemail.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).