Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: "Ömer Sinan Ağacan" <omeragacan@gmail.com>, gdb <gdb@sourceware.org>
Subject: Re: GDB C API -- does such a thing exist?
Date: Thu, 16 Oct 2014 13:54:00 -0000	[thread overview]
Message-ID: <20141016135413.GM4805@adacore.com> (raw)
In-Reply-To: <543FBFCE.4030305@redhat.com>

> No. Well let me qualify.  There is a libgdb, but I have never used it
> and I am not sure anyone has for some many years.  I am not sure how
> maintained it is either. Someone else might know more.

I don't think there is a libgdb anymore. IIRC, Jan eliminated it,
because it was increasing the amount of time needed to be linked
(first generate the .a, next build using the .a).

> A direct C API, aka what we have with Python, while nice, is not
> likely any time soon.  We cannot just expose all of the innards of GDB
> automatically, say with some script, to a C API.  GDB internals were
> never designed to be exposed in such a way.  The API would have to be
> a curated API and I don't see anyone working on that goal at present.
> 
> If you are determined to go the C route, IMO your best bet would be to
> modify GDB directly to your needs and rebuild.  GDB is fairly trivial
> to build.  Less so to modify, but those are your options at the
> moment. ;)

Be aware that there is no stability guaranteed in our C API.
Maybe lldb might provide better guarantees in that respect.
I would personally look at either Python or GDB/MI first.

-- 
Joel


  reply	other threads:[~2014-10-16 13:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 11:21 Ömer Sinan Ağacan
2014-10-16 13:45 ` Phil Muldoon
2014-10-16 13:54   ` Joel Brobecker [this message]
2014-10-16 14:06     ` Jan Kratochvil
2014-10-28 12:58   ` Jonas Maebe
2014-10-16 14:01 ` Bob Rossi
2014-10-16 14:09   ` Jan Kratochvil
2014-10-16 23:45 ` Stan Shebs
2014-10-17  6:45   ` Ömer Sinan Ağacan
2014-10-17  8:08     ` Pedro Alves
2014-10-17  8:47       ` Pedro Alves
2014-10-28 13:30         ` Jonas Maebe
2014-10-30 10:09           ` Pedro Alves
2014-10-17 12:06     ` Jan Kratochvil
2014-10-17 12:29       ` Joel Brobecker
2014-10-17 15:32         ` Bob Rossi
2014-10-17 12:02   ` Jan Kratochvil
2014-10-17 12:17   ` Jan Kratochvil

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=20141016135413.GM4805@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=omeragacan@gmail.com \
    --cc=pmuldoon@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