From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3576 invoked by alias); 9 Dec 2002 20:58:52 -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 3541 invoked from network); 9 Dec 2002 20:58:51 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 9 Dec 2002 20:58:51 -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 gB9KXNP16750 for ; Mon, 9 Dec 2002 15:33:23 -0500 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 gB9KwpD18682; Mon, 9 Dec 2002 15:58:51 -0500 Received: from dragon (romulus-int.sfbay.redhat.com [172.16.27.46]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id gB9Kwou22325; Mon, 9 Dec 2002 15:58:50 -0500 Subject: Re: Insight does nothing but popup "crash" windows From: "Martin M. Hunt" To: Phil Edwards Cc: "insight@sources.redhat.com" In-Reply-To: <20021209152759.A5986@disaster.jaj.com> References: <20021128190400.A24975@disaster.jaj.com> <1039459815.1145.2.camel@Dragon> <20021209152759.A5986@disaster.jaj.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 09 Dec 2002 12:58:00 -0000 Message-Id: <1039467673.29214.12.camel@Dragon> Mime-Version: 1.0 X-SW-Source: 2002-q4/txt/msg00175.txt.bz2 On Mon, 2002-12-09 at 12:27, Phil Edwards wrote: > 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" > You are debugging a core file. You cannot execute a core file, just inspect its state. Why did you try to set the target , set a breakpoint and run? Insight (and GDB) cannot do this. Perhaps Insight should be more intelligent, prevent this, display some useful help, etc. Once you start Insight with the core file, just open a stack window, register window, etc. You can browse the stack and stack variables. Martin