From: Tom Tromey <tromey@redhat.com>
To: Arjun Roy <roy.arjun@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Python Scripting Question
Date: Mon, 09 Nov 2009 21:12:00 -0000 [thread overview]
Message-ID: <m3bpjbfo2s.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4AF87557.8020701@stanford.edu> (Arjun Roy's message of "Mon, 09 Nov 2009 12:02:31 -0800")
>>>>> "Arjun" == Arjun Roy <roy.arjun@gmail.com> writes:
Arjun> It looks as though the two main things this would need would be to:
Arjun> 1. Be able to access the output one gets from executing a GDB command.
Arjun> Ideally one would get an object with various fields filled in based on
Arjun> the type of command, but for my purposes even a string would do - as
Arjun> long as the results can be accessed somehow.
Yeah, this has been on our wish-list for a while.
Basically we need to let python create two kinds of new ui-out objects:
one that writes the output to a python string, and another that is
mi-like and creates new python objects in response to output.
I have a tiny bit of code working toward this direction, but I never
finished it.
Arjun> 2. Some python objects for representing the current execution
Arjun> state of the program, where one could call methods for
Arjun> determining what's going on.
The SoC project addressed part of this. See the archer list archives
for information.
Arjun> How easy to hack in would this be?
I don't think anything here is too difficult; it just requires someone
to actually do it.
Tom
next prev parent reply other threads:[~2009-11-09 20:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 15:08 Arjun Roy
2009-11-09 17:16 ` Tom Tromey
2009-11-09 17:23 ` Tom Tromey
2009-11-09 17:44 ` Daniel Jacobowitz
2009-11-09 18:12 ` Tom Tromey
2009-11-09 20:22 ` Arjun Roy
2009-11-09 21:12 ` Tom Tromey [this message]
2009-11-13 14:36 ` scott snyder
2009-11-13 23:06 ` Arjun Roy
2009-11-18 20:43 ` 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=m3bpjbfo2s.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=roy.arjun@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