From: Daniel Jacobowitz <dan@codesourcery.com>
To: Jeroen Dobbelaere <jeroen.dobbelaere@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: gdb python and 'complete'
Date: Wed, 24 Mar 2010 17:16:00 -0000 [thread overview]
Message-ID: <20100324171559.GA9778@caradoc.them.org> (raw)
In-Reply-To: <325e93671003240824t3e940773ned358335b9fe1f40@mail.gmail.com>
On Wed, Mar 24, 2010 at 04:24:16PM +0100, Jeroen Dobbelaere wrote:
> Now, the 'complete' command is indeed retrieving all the member
> functions, but it will output them in the terminal in stead of feeding
> it back to 'member_list'.
>
> Is there a way to redirect the output, so that the python program can
> investigate it ?
I ended up having to log gdb output to a file and parse the file from
Python. But I think there's a clear argument that there should
be a generic way to get CLI output - and maybe more specific Python
routines for each command, e.g. a direct function for "complete".
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-03-24 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 15:24 Jeroen Dobbelaere
2010-03-24 15:54 ` Michel METZGER
2010-03-24 16:35 ` Jeroen Dobbelaere
2010-03-24 17:16 ` Daniel Jacobowitz [this message]
2010-03-24 17:59 ` Tom Tromey
2010-03-24 22:02 ` Jeroen Dobbelaere
2010-03-24 22:55 ` 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=20100324171559.GA9778@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=jeroen.dobbelaere@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