public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Steven Johnson <sbjohnson@ozemail.com.au>
Cc: insight@sourceware.cygnus.com
Subject: Re: insight/52
Date: Thu, 12 Oct 2000 14:54:00 -0000	[thread overview]
Message-ID: <39E63305.66156ECC@cygnus.com> (raw)
In-Reply-To: <39E62A7D.5CECCADD@ozemail.com.au>

Steven Johnson wrote:
> 
> I Had to change this to read
>        if {$gdb_running} {
>          return
>        }
> 
> Otherwise the TCL Interpreter hated it.
> 
Thanks, as I said, I had no way of testing it :)


> Did this, and download worked great. BUT...
> 
> Now I can Connect, and Download OK.
> 
> I Can insert a breakpoint and RUN OK.
> 
> If I then insert another breakpoint and CONTINUE.
> 
> The target runs and breaks, but Insight doesn't show the break having occured.
> I can change the source file and come back to the file it is broken in and the
> state changes for "GDB Running" to "GDB Halted" but the indicated line is
> wrong. (I can view the registers and the $pc is definately pointing to the next
> breakpoint instruction.)
> 
> I think it is something to do with the change we made to gdbtk_update, but i'm
> not sure what.
> 

Yeah, I was afraid that would happen but I hoped the gdb_running was going to be 
unset before gdbtk_update.

I will have to create a "safe_gdbtk_update" for the after commands and leave the
original alone.

I am sending you the patch momentarily.




-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@cygnus.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

       reply	other threads:[~2000-10-12 14:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20001012161301.19246.qmail@sourceware.cygnus.com>
     [not found] ` <39E62A7D.5CECCADD@ozemail.com.au>
2000-10-12 14:54   ` Fernando Nasser [this message]
2000-10-12 15:35   ` insight/52 Fernando Nasser

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=39E63305.66156ECC@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=sbjohnson@ozemail.com.au \
    /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).