From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15567 invoked by alias); 17 Apr 2009 07:59:10 -0000 Received: (qmail 15559 invoked by uid 22791); 17 Apr 2009 07:59:10 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_33 X-Spam-Check-By: sourceware.org Received: from smtp23.services.sfr.fr (HELO smtp23.services.sfr.fr) (93.17.128.20) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 17 Apr 2009 07:59:05 +0000 Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2326.sfr.fr (SMTP Server) with ESMTP id 12CF37000092; Fri, 17 Apr 2009 09:59:03 +0200 (CEST) Received: from [223.200.200.12] (121.138.84-79.rev.gaoland.net [79.84.138.121]) by msfrf2326.sfr.fr (SMTP Server) with ESMTP id CA6E77000090; Fri, 17 Apr 2009 09:59:02 +0200 (CEST) X-SFR-UUID: 20090417075902829.CA6E77000090@msfrf2326.sfr.fr Message-ID: <49E836C9.5050308@free.fr> Date: Fri, 17 Apr 2009 13:12:00 -0000 From: Marc Mason User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081204 SeaMonkey/1.1.14 MIME-Version: 1.0 To: Antony KING CC: gdb@sourceware.org Subject: Re: x commands in history References: <49E5ED01.5040300@free.fr> <20090415155857.GA14532@caradoc.them.org> <49E60736.4070407@free.fr> <49E72F63.1050201@st.com> In-Reply-To: <49E72F63.1050201@st.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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-04/txt/msg00140.txt.bz2 Antony KING wrote: > By any chance when you experience this problem is it when you use the > command console of Insight GUI interface ? Yes, I am using the GUI. gdb is started with the following command. sh4gdb -q -w -x foo.cmd -ex foo.bin > If so then this is a known issue. How do I tell which version of Insight I'm running? Has this bug been fixed in newer releases? NB: the "About GDB" item in the "Help" menu of the "Source Window" mentions "GNUPro Toolkit Insight Debugger" > Try using the TUI interface instead. I suppose I could do that, but it would be less convenient. I might have to learn to live with the bug. Thanks for the heads up. -- Regards.