public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: "Liang, James" <jliang@sandia.gov>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: RE: Developing for Insight
Date: Tue, 22 Apr 2003 21:18:00 -0000	[thread overview]
Message-ID: <1051046455.1534.28.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <71251C7D5FB1D2119C8F0008C7A44ED103792014@es07snlnt.sandia.gov>

On Tue, 2003-04-22 at 14:10, Liang, James wrote:
> Yes.. the tk gdbtk_update did it.  Hm.. I must have accidentally clobbered
> whatever normally calls that.

There could be another reason: Insight may not think you have an
inferior or something. When you run, does it ever hit gdbtk_tcl_idle in
gdb/gdbtk/library/interface.tcl? (Insert something like 'puts stdout
"here i am"' or 'dbug I "here i am"' into gdbtk_tcl_idle.)

What does "tk gdb_target_has_execution" output when you're stopped?

Keith


       reply	other threads:[~2003-04-22 21:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <71251C7D5FB1D2119C8F0008C7A44ED103792014@es07snlnt.sandia.gov>
2003-04-22 21:18 ` Keith Seitz [this message]
     [not found] <71251C7D5FB1D2119C8F0008C7A44ED103792016@es07snlnt.sandia.gov>
2003-04-22 23:15 ` Keith Seitz
     [not found] <71251C7D5FB1D2119C8F0008C7A44ED103792015@es07snlnt.sandia.gov>
2003-04-22 21:45 ` Keith Seitz
2003-04-22 21:47   ` Keith Seitz
2003-04-22 20:52 Liang, James
  -- strict thread matches above, loose matches on Subject: below --
2003-04-22 20:39 Liang, James
2003-04-22 20:58 ` Keith Seitz
2003-04-22 18:37 Liang, James
2003-04-22 18:45 ` Keith Seitz
2003-04-22 18:18 Liang, James
2003-04-22 18:43 ` Keith Seitz
2003-04-22 16:53 Liang, James
2003-04-22 17:52 ` Keith Seitz
2003-04-21 22:23 Liang, James
2003-04-21 22:59 ` Martin M. Hunt
2003-04-10 19:47 Liang, James
2003-04-10 20:05 ` Martin M. Hunt

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=1051046455.1534.28.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=jliang@sandia.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

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