From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24673 invoked by alias); 26 Nov 2009 15:54:58 -0000 Received: (qmail 24662 invoked by uid 22791); 26 Nov 2009 15:54:57 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from kuber.nabble.com (HELO kuber.nabble.com) (216.139.236.158) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 26 Nov 2009 15:54:49 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NDggC-00026c-Eo for gdb@sourceware.org; Thu, 26 Nov 2009 07:54:48 -0800 Message-ID: <26531395.post@talk.nabble.com> Date: Thu, 26 Nov 2009 18:28:00 -0000 From: fpga To: gdb@sourceware.org Subject: pexpect doesnt seem able to control bochs like it does gdb??? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-11/txt/msg00194.txt.bz2 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.