From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21296 invoked by alias); 29 Apr 2003 11:32:56 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 21279 invoked from network); 29 Apr 2003 11:32:55 -0000 Received: from unknown (HELO mercury.mv.net) (199.125.85.40) by sources.redhat.com with SMTP; 29 Apr 2003 11:32:55 -0000 Received: (qmail 13927 invoked from network); 29 Apr 2003 07:32:54 -0400 Received: from xbnh-2-40.mv.com (HELO ppro) (207.22.38.40) by mercury.mv.net with SMTP; 29 Apr 2003 07:32:54 -0400 X-Peer-Info: remote-ip 207.22.38.40 local-ip 199.125.85.40 local-name mercury.mv.net Message-ID: <045f01c30e43$17ee3270$c9d145cc@mrrmnh.adelphia.net> From: "Peter Reilley" To: References: <002f01c30e25$c7493b70$2401a8c0@charleshenri> Subject: Problem with Insight GUI mode Date: Tue, 29 Apr 2003 11:32:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-SW-Source: 2003-q2/txt/msg00049.txt.bz2 I have a problem with Insight 5.2.1 cross compiled for the ARM processor. Insight is running on X86 Linux. I am using Insight to connect to a remote target using Redhat's RDA. When it starts up only the RUN button is enabled, all the others are grayed out. When using Insight/GDB in this manner you cannot use the RUN command. If I open a command window and issue a STEP command, then everything is fine, the other buttons are enabled. I cannot fix this by putting commands in my .gdbinit file. The commands in the .gdbinit file execute properly but they do not cause the grayed out buttons to be enabled. Only issuing commands in the command window causes the condition to be cleared. This behavior probably make sense for native debugging but does not work for cross debugging. Is there any flag to Insight that changes this behavior? Any other fix? Thanks, Pete.