From: Edward Peschko <edwardp@excitehome.net>
To: Keith Seitz <keiths@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: using perl in gdbinit
Date: Wed, 28 Feb 2001 14:21:00 -0000 [thread overview]
Message-ID: <20010228142124.A28042@excitehome.net> (raw)
In-Reply-To: <Pine.SOL.3.91.1010228073240.19631D-100000@ryobi.cygnus.com>
>
> init_perl ()
> {
> g_interp = Perl_New_Interpreter ();
> }
>
> You should be able to do what you want (albeit in a hacky kind of way).
yeah, you could do this... and it might be a lot less hacky than anticipated,
if the perl module Inline could be used.
> For insight, we added a tcl interpreter and bound tcl's command parser to
> the gdb command "tk". We also have a tcl command, "gdb_cmd", which can be
> used to execute gdb commands in the tcl interpreter.
I didn't see it inside gdb-5.0... is it integrated with the standard
distribution or an add on?
> I could do things like what you want above (although I never have):
> (gdb) tk set help [gdb_cmd help]; puts stdout $help
> (gdb) tk set functions [gdb_cmd "info func main"]; puts stdout $functions
>
> Of course, you are still leaving yourself at the mercy of gdb's human
> readable output, so you'll need to parse gdb's output to do some things
> well.
hmm. that's what made me think of perl in the first place... one question
though, how does the tk interface deal with the 'more'-like behaviour of gdb
(ie: returns at the end of every page, etc.)
Ed
next prev parent reply other threads:[~2001-02-28 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 16:10 Edward Peschko
[not found] ` <Pine.SOL.3.91.1010228073240.19631D-100000@ryobi.cygnus.com>
2001-02-28 14:21 ` Edward Peschko [this message]
2001-02-28 14:33 ` Keith Seitz
2001-02-28 14:49 ` Edward Peschko
2001-02-28 15:03 ` Keith Seitz
2001-02-28 15:08 ` Russ Allbery
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=20010228142124.A28042@excitehome.net \
--to=edwardp@excitehome.net \
--cc=gdb@sources.redhat.com \
--cc=keiths@cygnus.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