public inbox for
help / color / mirror / Atom feed
From: Keith Seitz <>
Subject: Re: insight/345: Control buttons disabled while debugging remote TCP.
Date: Fri, 02 Oct 2009 00:43:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR insight/345; it has been noted by GNATS.

From: Keith Seitz <>
Subject: Re: insight/345: Control buttons disabled while debugging remote
Date: Thu, 01 Oct 2009 17:41:54 -0700

 On 10/01/2009 03:13 PM, Taylor, Jeff wrote:
 >   Did both:
 >   "tk set ::gdb_running" and
 >   "tk gdb_target_has_execution"
 >   Both return a "0" zero.
 That's what I expected. That means that there is a problem in the target 
 backend... The "gdb_target_has_execution" command checks:
    if (target_has_execution && ! ptid_equal (inferior_ptid, null_ptid))
      result = 1;
 So this condition is evaluating false on your target. I don't suppose 
 you could run insight under gdb and break in this function 
 (gdb_target_has_execution_command in gdbtk-cmds.c)? That would be very 
 helpful. My guess is inferior_ptid is the null_ptid. it should have been 
 set to a special non-null ptid when gdb was attached to the target.
 > How do I access a "snapshot" to be able to try something newer?
 Download it from the web site:
 We are due for (what may be the final) release in the next couple of 
 weeks, depending on how gdb is getting along, and if this is still a 
 problem, I'd really like to get it fixed once and for all.

             reply	other threads:[~2009-10-02  0:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02  0:43 Keith Seitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-10-01 22:13 Taylor, Jeff
2009-10-01 20:55 kseitz
2009-09-29 21:33 jeff.taylor

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