public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Grant Edwards <grante@visi.com>
Cc: insight@sources.redhat.com, Keith Seitz <keiths@cygnus.com>
Subject: Re: No step button using insight w/ remote target.
Date: Mon, 01 Oct 2001 08:25:00 -0000	[thread overview]
Message-ID: <3BEFE71D.1BA32DB6@cygnus.com> (raw)
In-Reply-To: <20011107172319.A2924@visi.com>

Grant Edwards wrote:
> 
> I'm using 5.0.92 from the development snapshot ftp directory
> configured for arm-elf target Linux RH6.2 host.  The target is
> an ARM7 single-board computer running RedBoot w/ GDB stubs.
> 
> Evertying works swimmingly in -nw mode.
> 
> Without the -nw option I run into a couple of problems:
> 
>  1) Doing a "target remote /dev/ttyS1" command in the console
>     hangs gdb completely.
> 
>  2) Downloading with the "target" menu using the "continue" run
>     method and "set breakpoint" works OK, but when the
>     breakpoint is hit, none of the step, next, continue,
>     buttons are enabled.
> 
>     Doing "step" or "next" from the console works fine, and I
>     can set breakpoints by clicking in the source window, but
>     the button-bar seems to be stuck in the wrong state.
> 

It seems that the notification that the target has stopped is not
reaching the menu and toolbar objects...

Grant, can you please start the Debug Window before you connect
and let us know what is in there?

If you set:
GDBTK_DEBUG
to 1, you'll have a Debug Window option in your View menu.  You can
open it before you connect.

I am not sure what is in your version.  Maybe you can also have a
log written by setting 
GDBTK_DEBUGFILE
to a file and setting the GDBTK_DEBUG to 1.

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

WARNING: multiple messages have this Message-ID
From: Fernando Nasser <fnasser@cygnus.com>
To: Grant Edwards <grante@visi.com>
Cc: insight@sources.redhat.com, Keith Seitz <keiths@cygnus.com>
Subject: Re: No step button using insight w/ remote target.
Date: Mon, 12 Nov 2001 07:13:00 -0000	[thread overview]
Message-ID: <3BEFE71D.1BA32DB6@cygnus.com> (raw)
Message-ID: <20011112071300.01gV4XXdWi4nDx1wb1SgDjiYTznk_ARnB_kFHTVHjmA@z> (raw)
In-Reply-To: <20011107172319.A2924@visi.com>

Grant Edwards wrote:
> 
> I'm using 5.0.92 from the development snapshot ftp directory
> configured for arm-elf target Linux RH6.2 host.  The target is
> an ARM7 single-board computer running RedBoot w/ GDB stubs.
> 
> Evertying works swimmingly in -nw mode.
> 
> Without the -nw option I run into a couple of problems:
> 
>  1) Doing a "target remote /dev/ttyS1" command in the console
>     hangs gdb completely.
> 
>  2) Downloading with the "target" menu using the "continue" run
>     method and "set breakpoint" works OK, but when the
>     breakpoint is hit, none of the step, next, continue,
>     buttons are enabled.
> 
>     Doing "step" or "next" from the console works fine, and I
>     can set breakpoints by clicking in the source window, but
>     the button-bar seems to be stuck in the wrong state.
> 

It seems that the notification that the target has stopped is not
reaching the menu and toolbar objects...

Grant, can you please start the Debug Window before you connect
and let us know what is in there?

If you set:
GDBTK_DEBUG
to 1, you'll have a Debug Window option in your View menu.  You can
open it before you connect.

I am not sure what is in your version.  Maybe you can also have a
log written by setting 
GDBTK_DEBUGFILE
to a file and setting the GDBTK_DEBUG to 1.

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

  reply	other threads:[~2001-11-12 15:13 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-07 15:19 Grant Edwards
2001-10-01  8:25 ` Fernando Nasser [this message]
2001-10-02 14:22   ` Grant Edwards
2001-11-15 15:46     ` Grant Edwards
2001-10-02 15:40   ` Grant Edwards
2001-11-19  8:32     ` Grant Edwards
2001-11-12  7:13   ` Fernando Nasser
2001-10-02 16:10 ` Keith Seitz
2001-10-02 20:18   ` Grant Edwards
2001-10-03  9:37     ` Keith Seitz
2001-10-03 10:54       ` Grant Edwards
2001-10-03 11:09         ` Keith Seitz
2001-10-03 11:20           ` Grant Edwards
2001-10-03 11:47             ` Keith Seitz
2001-10-03 13:22               ` Grant Edwards
2001-10-03 14:03                 ` Keith Seitz
2001-10-03 15:50                   ` Grant Edwards
2001-11-19 14:12                     ` Grant Edwards
2001-11-19 13:28                   ` Keith Seitz
2001-11-19 13:19                 ` Grant Edwards
2001-10-03 16:31               ` Grant Edwards
2001-10-04 11:28                 ` Grant Edwards
2001-11-20 16:16                   ` Grant Edwards
2001-11-19 14:39                 ` Grant Edwards
2001-11-19 13:05               ` Keith Seitz
2001-11-19 13:03             ` Grant Edwards
2001-11-19 12:55           ` Keith Seitz
2001-11-19 12:49         ` Grant Edwards
2001-11-19 12:17       ` Keith Seitz
2001-11-19 12:06     ` Grant Edwards
2001-11-19 12:00   ` Keith Seitz

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=3BEFE71D.1BA32DB6@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=grante@visi.com \
    --cc=insight@sources.redhat.com \
    --cc=keiths@cygnus.com \
    /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).