From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19928 invoked by alias); 2 Oct 2003 16:05:23 -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 19921 invoked from network); 2 Oct 2003 16:05:22 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 2 Oct 2003 16:05:22 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h92G5M120711 for ; Thu, 2 Oct 2003 12:05:22 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h92G5Mc10680; Thu, 2 Oct 2003 12:05:22 -0400 Received: from [150.1.200.14] (vpn50-62.rdu.redhat.com [172.16.50.62]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id h92G5Lbe001186; Thu, 2 Oct 2003 12:05:21 -0400 Subject: Re: File etc. Toolbar sometimes Missing from Source Window (Cygwin) From: Keith Seitz To: Andy Lindsay Cc: "insight@sources.redhat.com" In-Reply-To: References: Content-Type: text/plain Organization: Message-Id: <1065110892.1584.9.camel@lindt.uglyboxes.com> Mime-Version: 1.0 Date: Thu, 02 Oct 2003 16:05:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2003-q4/txt/msg00006.txt.bz2 On Thu, 2003-10-02 at 06:32, Andy Lindsay wrote: > If I exit Insight with the local variables window shown then the next > time I open Insight the source file window doesn't show the bar with > File, Function and Source/Mixed... dropdowns. If I adjust the height of > the window by grabbing the title bar then the bar appears. > > If I close the local variables window before exiting Insight then the > next time I open Insight the bar appears correctly. > This is certainly very unusual. First time I've heard of such a thing. But then, I haven't really used insight much in the last year, since I've been stricken with the Java curse... Set GDBTK_DEBUG to non-zero in your environment before launching insight. You will get a log file of the debugging output (a file called "insight.log". Do this when the error is generated and when it is not. Any differences in the messages? Keith