This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Re: No step button using insight w/ remote target.
- To: Grant Edwards <grante at visi dot com>
- Subject: Re: No step button using insight w/ remote target.
- From: Fernando Nasser <fnasser at cygnus dot com>
- Date: Mon, 12 Nov 2001 10:13:33 -0500
- Cc: insight at sources dot redhat dot com, Keith Seitz <keiths at cygnus dot com>
- Organization: Red Hat , Inc. - Toronto
- References: <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