Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: fpga <mgbg25171@blueyonder.co.uk>
To: gdb@sourceware.org
Subject: Re: controlling gdb via python's pexpect
Date: Fri, 06 Nov 2009 09:12:00 -0000	[thread overview]
Message-ID: <26227761.post@talk.nabble.com> (raw)
Message-ID: <20091106091200.5LeuQJwdyp6PSVwtpktXOp9ENlaiG_0Pcaqnt7oMRGU@z> (raw)



fpga wrote:
> 
> Can someone please give me an example of how this is done.
> I'm afraid the documentation is not helping me.
> Thx
> 

Thx George
You've got further than I have!
I tried to use subprocess before trying pexpect but failed.
pexpect was suggested by experts on the python forum.
Unfortuntely they appear incapable of correcting my trivial example of
opening a terminal and sending the command 'gdb' to it.
Any snippets most welcome.
Looking at my repositories I see libdevel-gdb-perl.
I like python's orderliness but have noticed that when python fails perl
usually delivers.
-- 
View this message in context: http://old.nabble.com/controlling-gdb-via-python%27s-pexpect-tp26221261p26227761.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.


         reply	other threads:[~2009-11-06  7:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05 20:27 fpga
2009-11-05 20:35 ` George Russell
2009-11-06 10:56   ` Gaius Mulley
2009-11-06 10:56     ` Gaius Mulley
2009-11-06 11:07     ` fpga
2009-11-06 16:55       ` Gaius Mulley
2009-11-06 17:57         ` fpga
2009-11-06  9:11 ` fpga [this message]
2009-11-06  7:15   ` fpga
2009-11-06  9:12   ` fpga
2009-11-06 10:23   ` fpga
2009-11-06 10:28   ` George Russell
2009-11-06 10:39   ` Greg Law
2009-11-06 10:44 ` fpga

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=26227761.post@talk.nabble.com \
    --to=mgbg25171@blueyonder.co.uk \
    --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