From: fpga <mgbg25171@blueyonder.co.uk>
To: gdb@sourceware.org
Subject: pexpect doesnt seem able to control bochs like it does gdb???
Date: Thu, 26 Nov 2009 18:28:00 -0000 [thread overview]
Message-ID: <26531395.post@talk.nabble.com> (raw)
I've been controlling qemu with gdb via pexpect.
I'm now trying to control bochs debugger with pexpect
[code]
#!/usr/bin/python
import pexpect, subprocess, time
child = pexpect.spawn('terminator -x bochs\n')
child.expect_exact ('Please choose one: [6] ')
child.send ('6\n')
[/code]
Unfortunately bochs debugger ignores the 6 that is sent.
I just wonder if anyone knows how to get around such "ignorance".
If it's any help...
I note that if I If I press 6 then this works
i.e. it's as if I had inserted 'child.interact()' before sending the 6???
Any advice much appreciated
--
View this message in context: http://old.nabble.com/pexpect-doesnt-seem-able-to-control-bochs-like-it-does-gdb----tp26531395p26531395.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
next reply other threads:[~2009-11-26 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 18:28 fpga [this message]
2009-11-26 18:32 ` Joel Brobecker
2009-11-26 21:35 ` Gaius Mulley
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=26531395.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