Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nala Ginrut <mulei@gnu.org>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: About adding new script language
Date: Tue, 30 Apr 2013 07:49:00 -0000	[thread overview]
Message-ID: <1367308142.25105.25.camel@Renee-desktop.suse> (raw)

[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]

Hi GDB folks!
I'm new comer here, and I'm trying to make guile the extension language.
Anyway, folks could use python as well, before guile has reliable python
front-end.
I've read the python part, here're some ideas, correct me if I'm wrong
please. ;-)

1. Is it necessary to use language_defn to define the extension
language?
My understanding is language_defn defines a new language support for
debugging the defined language, not to define a new extension language
for other debugging purpose. Or not?
For example, go-lang.c is the support for debugging go, not add go as
the debug script language, just like python. But it confused me that
python has used language_defn.

2. There should be interfaces to add the script language, but I didn't
find it, anyone point me out? I don't think I have to write new
lexer/parser for that, just need a way to get the expr and call guile's
read function. Thanks!

3. My aim is not only add guile as an extension in gdb's REPL, but a
more powerful language for the automatic debugging. For that purpose,
the hard/heavy work is not to add guile into gdb, but a framework
project implemented by guile based on the support of guile-gdb. 
Is this idea too unrealistic?

Happy hacking!
Thanks!



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2013-04-30  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30  7:49 Nala Ginrut [this message]
     [not found] ` <CADPb22Qoz7-fDCXq=5eiw_OA8VQDOOji_AETrxBy+d_AR0jDdg@mail.gmail.com>
2013-05-01  3:49   ` Nala Ginrut
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=1367308142.25105.25.camel@Renee-desktop.suse \
    --to=mulei@gnu.org \
    --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