From: Nala Ginrut <mulei@gnu.org>
To: Doug Evans <dje@google.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: About adding new script language
Date: Wed, 01 May 2013 03:49:00 -0000 [thread overview]
Message-ID: <1367380182.25105.105.camel@Renee-desktop.suse> (raw)
In-Reply-To: <CADPb22Qoz7-fDCXq=5eiw_OA8VQDOOji_AETrxBy+d_AR0jDdg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
hi Doug! Thanks for reply!
On Tue, 2013-04-30 at 17:51 -0700, Doug Evans wrote:
> There aren't any interfaces, they need to be added.
> One of the hardest parts of adding Guile support to GDB (as an
> extension language)
> will be providing reasonable interfaces.
>
Could you give me some hints where is the preferable place to cut in?
Here're my questions:
1. Find a way to get the input string and pass it to guile for eval when
'Guile mode' enabled. I know python module has some functions to handle
this, but I don't know how the things from GDB passed in. Maybe some
hooks in GDB REPL?
2. When in 'Guile mode', there should be a way to get the context info
of gdb. I know python could do it with gdb module, like 'gdb.a' to get
the variable named 'a'. My question is how to interact with GDB context?
Any docs for that?
3. According to our previous discussion, there's no need to write a
general interfaces for extension language (maybe not?). So I think the
easier way is to find out what's in GDB is most useful thing, and write
the wrapper for Guile. Any suggestion?
4. If we do need to add the clean interfaces, what part of code should I
take a look?
Thanks!
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-05-01 3:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 7:49 Nala Ginrut
[not found] ` <CADPb22Qoz7-fDCXq=5eiw_OA8VQDOOji_AETrxBy+d_AR0jDdg@mail.gmail.com>
2013-05-01 3:49 ` Nala Ginrut [this message]
2013-05-01 4:31 ` Doug Evans
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=1367380182.25105.105.camel@Renee-desktop.suse \
--to=mulei@gnu.org \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
/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