From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18896 invoked by alias); 9 Dec 2002 20:28:01 -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 18885 invoked from network); 9 Dec 2002 20:28:01 -0000 Received: from unknown (HELO disaster.jaj.com) (66.93.21.106) by sources.redhat.com with SMTP; 9 Dec 2002 20:28:01 -0000 Received: (from phil@localhost) by disaster.jaj.com (8.11.4/8.11.4) id gB9KRx706055; Mon, 9 Dec 2002 15:27:59 -0500 Date: Mon, 09 Dec 2002 12:28:00 -0000 From: Phil Edwards To: "Martin M. Hunt" Cc: "insight@sources.redhat.com" Subject: Re: Insight does nothing but popup "crash" windows Message-ID: <20021209152759.A5986@disaster.jaj.com> References: <20021128190400.A24975@disaster.jaj.com> <1039459815.1145.2.camel@Dragon> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1039459815.1145.2.camel@Dragon>; from hunt@redhat.com on Mon, Dec 09, 2002 at 10:50:14AM -0800 X-SW-Source: 2002-q4/txt/msg00174.txt.bz2 On Mon, Dec 09, 2002 at 10:50:14AM -0800, Martin M. Hunt wrote: > On Thu, 2002-11-28 at 16:04, Phil Edwards wrote: > > > > I find myself needing to debug a program, and it's just too complicated > > for the character-based GDB, so I built CVS GDB with the gui enabled. > > > > Initially it failed to run the program because the target was not valid. > > After I figured out that I needed to set the target to "exec" myself, > > and did that, the weirdness began. > > Can you provide us any clues here? What target? What OS? A program compiled for native i686/Linux, nothing special. > What do you > mean by "the target was not valid"? The first time I tried to debug it, that's what GDB/Insight told me. After poking about in the menus I found that the default seems to be for some kind of remote debugging. I changed the target from a blank selection to "Exec" on a guess, and then it worked. > What exactly did you do? "gdb -w ./a.cout core" > Can you > start debugging your program using just GDB? Yes, but it quickly becomes incomprehensible. Stepping through the iostreams hierarchy calls without, for example, a seperate stack window, is almost hopeless. Phil -- I would therefore like to posit that computing's central challenge, viz. "How not to make a mess of it," has /not/ been met. - Edsger Dijkstra, 1930-2002