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

["Taylor, Jeff" <jeff.taylor@tqs.com>]

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

From: "Taylor, Jeff" <jeff.taylor@tqs.com>
To: <kseitz@sources.redhat.com>,
	<insight-prs@sources.redhat.com>,
	"Taylor, Jeff" <jeff.taylor@tqs.com>,
	<nobody@sources.redhat.com>,
	<insight-gnats@sources.redhat.com>
Cc:  
Subject: RE: insight/345: Control buttons disabled while debugging remote TCP.
Date: Thu, 1 Oct 2009 15:04:24 -0700

 Did both:
 "tk set ::gdb_running" and
 "tk gdb_target_has_execution"
 
 Both return a "0" zero.
 
 How do I access a "snapshot" to be able to try something newer?
 
 I think this has been a problem for quite a while. I've used several
 insight versions over the years and it has always been touch-n-go as to
 whether those debugger buttons became active. Used to be a simple single
 step command after loading the code would activate them. Not any more.=20
 
 
 Jeff Taylor | RFID Applications & Development  | TriQuint Semiconductor=20
 500 W. Renner Road | Richardson, TX 75080 | ( 214-797-9581 | *
 jeff.taylor@tqs.com
 
 
 -----Original Message-----
 From: kseitz@sources.redhat.com [mailto:kseitz@sources.redhat.com]=20
 Sent: Thursday, October 01, 2009 3:55 PM
 To: insight-prs@sources.redhat.com; Taylor, Jeff;
 kseitz@sources.redhat.com; nobody@sources.redhat.com
 Subject: Re: insight/345: Control buttons disabled while debugging
 remote TCP.
 
 Synopsis: Control buttons disabled while debugging remote TCP.
 
 Responsible-Changed-From-To: unassigned->kseitz
 Responsible-Changed-By: kseitz
 Responsible-Changed-When: Thu Oct  1 20:55:07 2009
 Responsible-Changed-Why:
     mine
 State-Changed-From-To: open->analyzed
 State-Changed-By: kseitz
 State-Changed-When: Thu Oct  1 20:55:07 2009
 State-Changed-Why:
     This could be caused by a multitude of problems -- most of them in
 gdb.
    =20
     To start, while sitting at a breakpoint (attached to your target, at
 least), open a console window and enter "tk set ::gdb_running" and "tk
 gdb_target_has_execution". What do those return?
    =20
     Have you tried a snapshot? The problem might already be fixed. [It's
 hard to tell exactly because 6.8 is already a couple of years old.]
 
 http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&databa=
 s
 e=3Dinsight&pr=3D345