From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <insight-return-4666-listarch-insight=sources.redhat.com@sources.redhat.com>
Received: (qmail 25478 invoked by alias); 20 Oct 2003 20:10:52 -0000
Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:insight-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/insight/>
List-Post: <mailto:insight@sources.redhat.com>
List-Help: <mailto:insight-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: insight-owner@sources.redhat.com
Received: (qmail 25054 invoked from network); 20 Oct 2003 20:10:50 -0000
Received: from unknown (HELO opal.franklin.com) (63.88.59.84)
  by sources.redhat.com with SMTP; 20 Oct 2003 20:10:50 -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 h9KKAi0m023380;
	Mon, 20 Oct 2003 16:10:44 -0400 (EDT)
Received: (from duane@localhost)
	by europa.franklin.com (8.11.6/8.9.3) id h9KKAj121044;
	Mon, 20 Oct 2003 16:10:45 -0400
Date: Mon, 20 Oct 2003 20:10:00 -0000
Message-Id: <200310202010.h9KKAj121044@europa.franklin.com>
From: Duane Ellis <duane@franklin.com>
To: keiths@redhat.com
CC: insight@sources.redhat.com
In-reply-to: <1066680027.1583.47.camel@lindt.uglyboxes.com> (message from
	Keith Seitz on 20 Oct 2003 13:00:27 -0700)
Subject: Re: Multiple ~/.gdbtkinit files
Reply-to: duane@franklin.com
References: <200310201854.h9KIswh08731@europa.franklin.com>
	 <1066676597.1589.15.camel@lindt.uglyboxes.com>
	 <200310201950.h9KJo5L19370@europa.franklin.com> <1066680027.1583.47.camel@lindt.uglyboxes.com>
X-SW-Source: 2003-q4/txt/msg00048.txt.bz2


>> So what is conflicting that you need multiple .gdbtkinit files? [My

We have 3 different internal Insight targets - all custom ports to
internally developed custom cpus.. one of them - was used our eBookman
product. Perhaps you saw this a couple years ago.

>> 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).

Where do I do this at?

I could sure use this right now - I'm fighting a problem with CYGWIN
where the source window stops working.

>> 2. Use "puts stdout" or "puts stderr" to force output to console. (This
   doesn't work on cygwin, though.)

Agh... I know.... what a pain.

-Duane.