Re: insight/345: Control buttons disabled while debugging remote TCP.

[Keith Seitz <keiths@redhat.com>]

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

From: Keith Seitz <keiths@redhat.com>
To: insight-gnats@sourceware.org
Cc:  
Subject: Re: insight/345: Control buttons disabled while debugging remote
 TCP.
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:
 
 ftp://sourceware.org/pub/insight/snapshots/current
 
 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.
 
 Keith