From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7710 invoked by alias); 30 Nov 2006 23:05:10 -0000 Received: (qmail 7686 invoked by uid 48); 30 Nov 2006 23:05:10 -0000 Date: Thu, 30 Nov 2006 23:05:00 -0000 Message-ID: <20061130230510.7685.qmail@sourceware.org> To: dave.bryan@gmail.com, insight-prs@sources.redhat.com, kseitz@sources.redhat.com, nobody@sources.redhat.com From: kseitz@sources.redhat.com Reply-To: kseitz@sources.redhat.com, dave.bryan@gmail.com, insight-prs@sources.redhat.com, kseitz@sources.redhat.com, nobody@sources.redhat.com, insight-gnats@sources.redhat.com X-Mailer: gnatsweb 2.9.3 Subject: Re: insight/301: Insight toolbar buttons disabled Mailing-List: contact insight-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-prs-owner@sourceware.org X-SW-Source: 2006-q4/txt/msg00007.txt.bz2 Synopsis: Insight toolbar buttons disabled Responsible-Changed-From-To: unassigned->kseitz Responsible-Changed-By: kseitz Responsible-Changed-When: Thu Nov 30 23:05:10 2006 Responsible-Changed-Why: mine State-Changed-From-To: open->analyzed State-Changed-By: kseitz State-Changed-When: Thu Nov 30 23:05:10 2006 State-Changed-Why: I don't recommend doing what you are doing in your gdb script file. There is simply no need: Insight will do that for you. [Nit: You really should not use symbol-file alone. All that does is read symbol information. You get no msymbols that way... Use the "file" command so that you get both code and symbols loaded.] Go to File->Target Settings and fill in the all the boxes. Simply press run and insight will do everything listed in your script file. When you exit, insight will save all those settings, so that when you restart, you simply have to press run again. [Of course, if you use this on multiple different executables, you'll have to do this once for each...] Other problem might be that you're using tracing. Is Insight set to tracing mode? [I don't even know if that works any more...] That would probably help a lot. Look in Preferences->Global. As for the problem at hand, I believe that occurs because insight is confused about the state of the target, since the command file will run BEFORE insight is initialized. As of now, I don't know of any fix. That's not to say there might not be one, but I just don't know of any off the top of my head. I know I gave up on this a (long) while ago in frustration. For the time being, I'm leaving this bug open. http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=301