From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22958 invoked by alias); 20 Oct 2003 19:57:19 -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 22930 invoked from network); 20 Oct 2003 19:57:18 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 20 Oct 2003 19:57:18 -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 h9KJvHM07489 for ; Mon, 20 Oct 2003 15:57:17 -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 h9KJvHr20599; Mon, 20 Oct 2003 15:57:17 -0400 Received: from [150.1.200.14] (vpn50-73.rdu.redhat.com [172.16.50.73]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id h9KJvGwC028959; Mon, 20 Oct 2003 15:57:16 -0400 Subject: Re: Multiple ~/.gdbtkinit files From: Keith Seitz To: duane@franklin.com Cc: "insight@sources.redhat.com" In-Reply-To: <200310201950.h9KJo5L19370@europa.franklin.com> References: <200310201854.h9KIswh08731@europa.franklin.com> <1066676597.1589.15.camel@lindt.uglyboxes.com> <200310201950.h9KJo5L19370@europa.franklin.com> Content-Type: text/plain Organization: Message-Id: <1066680027.1583.47.camel@lindt.uglyboxes.com> Mime-Version: 1.0 Date: Mon, 20 Oct 2003 19:57:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2003-q4/txt/msg00047.txt.bz2 On Mon, 2003-10-20 at 12:50, Duane Ellis wrote: > >> Anyway, you could try something like: > > The -nx and --command options are not the problem, they deal with the > normal ".gdb<>init" file. Doh, you're right. That's not what you wanted. My bad. > >> So you have, for instance, different window geometries and open > windows based on the target? > > Not that I know of. So what is conflicting that you need multiple .gdbtkinit files? [My memory of preferences is slipping away, so be gentle. :-)] > 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. Hmmm. I thought that one could always work around the problem one of two ways (on *nix, at least): 1. use lots of "dbug" statements and set GDBTK_LOGFILE (or is it GDBTK_DEBUG? both? I don't recall). Using a log file would get you output sooner (as I seem to recall). 2. Use "puts stdout" or "puts stderr" to force output to console. (This doesn't work on cygwin, though.) Keith