public inbox for
help / color / mirror / Atom feed
Subject: Re: insight/301: Insight toolbar buttons disabled
Date: Thu, 30 Nov 2006 23:05:00 -0000	[thread overview]
Message-ID: <> (raw)

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
State-Changed-From-To: open->analyzed
State-Changed-By: kseitz
State-Changed-When: Thu Nov 30 23:05:10 2006
    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.

             reply	other threads:[~2006-11-30 23:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30 23:05 kseitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-12 12:33 dave.bryan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).