From: Dmitry Samersoff <dms@samersoff.net>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Hui Zhu <teawater@gmail.com>,
"gdb@sourceware.org" <gdb@sourceware.org>,
abhijit.k.halder@gmail.com
Subject: Re: How to write native (i.e. C/C++) plugin for gdb?
Date: Wed, 25 Dec 2013 15:32:00 -0000 [thread overview]
Message-ID: <52BAFA96.8060407@samersoff.net> (raw)
In-Reply-To: <20131224144704.GJ4558@adacore.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Joel,
Thank you for the response.
I found this patch
https://sourceware.org/ml/gdb-patches/2012-05/msg00500.html - many
thanks to Abhijit.
1. What is the reason to keep it off main trunk? Is there a chance to
have it changed?
2. What API is available from within a plugin? i.e. how I can access
coredump memory?
- -Dmitry
On 2013-12-24 18:47, Joel Brobecker wrote:
>> I need to implement scenario like one below:
>>
>> (gdb) load-plugin libgdbjvm.so (gdb) attach PID (gdb) jvm show
>> loaded-classes (gdb) jvm show java-threads (gdb) jvm show
>> code-cache
>
> Maybe you could add some routines in your program that are solely
> intended for debugging purposes, and then define commands that call
> those routines. Off hand, that's the only way I can think of.
> Otherwise, interface the C++ stuff you need from Python - if
> necessary, export some stuff to C?
>
- --
Dmitry Samersoff
Saint Petersburg, Russia, http://devnull.samersoff.net
* There will come soft rains ...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSuvqWAAoJEHEy08c4gIABMUQH/AiXTuX8BWuzG+Vm19EOSHlb
2EuBEpo633nBTgUlKIj99ePfuh5jRwZ5R0/pBmM/Ue4ytCJWTu0iQl5OU3RQ81BT
U9lFccSUW9oBnrfCqAZWQLss2sX1eL+9JjCduu47rKa4mLMaiJ0kxRml7IAT42Lo
h9j2QZSBcmEd5nA0VITU1meeIoU+KPhVe/UpNu1e3g/0EBgTnZbZ6iBbzqh+QhiY
lzR4g3KtNpI7mz4DvJ8O7+xNbSeh5sU2zWWG/EbETQHkp/Xt/AbChnSY5udFe1oS
lT87bTgh3cqWnTJVWa6UMI98K+RwIFVvxNQ3pIkuFFUh7HwEo+ubJL5xQT0Pn8Y=
=Ql5e
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-12-25 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 12:31 Dmitry Samersoff
2013-12-24 13:16 ` Hui Zhu
2013-12-24 14:13 ` Dmitry Samersoff
2013-12-24 14:47 ` Joel Brobecker
2013-12-25 15:32 ` Dmitry Samersoff [this message]
2013-12-25 16:51 ` Dmitry Samersoff
2013-12-26 22:55 ` Doug Evans
2013-12-27 14:15 ` Dmitry Samersoff
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=52BAFA96.8060407@samersoff.net \
--to=dms@samersoff.net \
--cc=abhijit.k.halder@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=teawater@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