From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14885 invoked by alias); 20 Oct 2003 19:50:10 -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 14771 invoked from network); 20 Oct 2003 19:50:05 -0000 Received: from unknown (HELO opal.franklin.com) (63.88.59.84) by sources.redhat.com with SMTP; 20 Oct 2003 19:50:05 -0000 Received: from europa.franklin.com (europa [192.9.200.131]) by opal.franklin.com (8.12.10+Sun/8.12.10) with ESMTP id h9KJo40m022657 for ; Mon, 20 Oct 2003 15:50:04 -0400 (EDT) Received: (from duane@localhost) by europa.franklin.com (8.11.6/8.9.3) id h9KJo5L19370; Mon, 20 Oct 2003 15:50:05 -0400 Date: Mon, 20 Oct 2003 19:50:00 -0000 Message-Id: <200310201950.h9KJo5L19370@europa.franklin.com> From: Duane Ellis To: insight@sources.redhat.com In-reply-to: <1066676597.1589.15.camel@lindt.uglyboxes.com> (message from Keith Seitz on 20 Oct 2003 12:03:17 -0700) Subject: Re: Multiple ~/.gdbtkinit files Reply-to: duane@franklin.com References: <200310201854.h9KIswh08731@europa.franklin.com> <1066676597.1589.15.camel@lindt.uglyboxes.com> X-SW-Source: 2003-q4/txt/msg00046.txt.bz2 >> Anyway, you could try something like: The -nx and --command options are not the problem, they deal with the normal ".gdb<>init" file. I'm talking about the gdb<>init file (or gdbtk.ini file on windows) there is no command line option to disable that one. It is 100% handled by the prefs.tcl file. It seems that if I delete this file - things work again when they break. If I don't - things go horribly wrong. >> So you have, for instance, different window geometries and open windows based on the target? Not that I know of. The really tough thing is - I can't seem to debug tcl startup problems under insight. For instance, if you have a syntax error somewhere, or any erorr message, it gets swallowed up and not shown to you. You have to debug this stuff blind. -- On a side note -- This problem is not limited to Insight - we have RH6.2 on some machines, and RH7.3 on others. and we remote-X into them from other machines. (Depends on where I am at my desk, or in the hardware lab, etc) What is a *REAL* pain in the but is when GNOME or KDE discovers that you have an old "GNOME" init file - then upgrades it for you - then you go to another machine and it won't start because it runs an older version of GNOME. Central to that problem is a shared home directory throughout our systems. It's both a blessing and a curse. Both RH6.2 and RH7.3 don't like it when you login 2 times via remote-X from two different locations..... ie: You go into the hardware lab and login, while remaining logged in at your desk) -Duane.