public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: "Ö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:45:00 -0000	[thread overview]
Message-ID: <543FBFCE.4030305@redhat.com> (raw)
In-Reply-To: <CAMQQO3=gR_6=D__Q_rn2Q8LQmE+bdokhAmbKh6fEkkNMH42fxA@mail.gmail.com>

On 16/10/14 12:20, Ömer Sinan Ağacan wrote:
> Do we have a C API for GDB? Something that allows me to run all the
> GDB commands/functions that I can run in GDB prompt, but without
> messing with GDB prompt?
>
> Python API is not great for what I want to do. I want to run GDB
> inside a program, search for some specific currently-running
> processes, attach to them, add some breakpoints etc. although all of
> those are possible with Python API, 1) I'm not huge fan of the
> language 2) I feel like most things would be a lot easier if I could
> use a C API that allows me to drive GDB itself.

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.

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. ;)

As it is, for scripting with have Python and Guile based scripting.

Cheers,

Phil


  reply	other threads:[~2014-10-16 13:45 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 [this message]
2014-10-16 13:54   ` Joel Brobecker
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=543FBFCE.4030305@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=omeragacan@gmail.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).