From: Bruce Korb <bruce.korb@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tromey@redhat.com>,
Abhijit Halder <abhijit.k.halder@gmail.com>,
gdb@sourceware.org
Subject: Re: custom runtime GDB extensions
Date: Tue, 23 Oct 2012 20:01:00 -0000 [thread overview]
Message-ID: <CAKRnqNJWqjJebsqb-xo81GL5h53z3n9VKjroPwM6wSqGajfUSQ@mail.gmail.com> (raw)
In-Reply-To: <20121023194943.GE3571@adacore.com>
On Tue, Oct 23, 2012 at 12:49 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> A pointer to a cook book would be really helpful. Thank you so much!
>
> My point of view of a "cookbook" solution to extending GDB would be to
> use the Python extension interface. It does depend on having a GDB that
> includes Python support, but python suppport has been around for a while,
> now, so I do not think it is an unreasonable assumption.
OK, I do not speak Python. I have a library of C code that does what I need.
Since no distribution I regularly use regularly enables python extensions for
GDB, I will, therefore, need to rebuild GDB with python enabled and I need
to find how to code up python-into-shared-library calls. Likely also how to
load said shared library. That is a lot of work just for a GDB-into-object-code
glue layer. I'll do it, but please help me with a short cut that does
not entail
the deep recesses of Python for dlopen-ing and calling into shared libraries.
An example would do very nicely. I have googled for this and the lack of
results has me here. Again, please and thank you! :) Regards, Bruce
next prev parent reply other threads:[~2012-10-23 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 23:35 Bruce Korb
2012-10-22 21:01 ` Tom Tromey
2012-10-22 22:01 ` Bruce Korb
2012-10-23 19:10 ` Tom Tromey
2012-10-23 19:42 ` Bruce Korb
2012-10-23 19:49 ` Joel Brobecker
2012-10-23 20:01 ` Bruce Korb [this message]
2012-10-23 20:28 ` Tom Tromey
2012-10-23 20:54 ` Bruce Korb
2012-10-23 21:01 ` Tom Tromey
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=CAKRnqNJWqjJebsqb-xo81GL5h53z3n9VKjroPwM6wSqGajfUSQ@mail.gmail.com \
--to=bruce.korb@gmail.com \
--cc=abhijit.k.halder@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=tromey@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