From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9626 invoked by alias); 12 Nov 2001 15:13:57 -0000 Mailing-List: contact insight-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 9473 invoked from network); 12 Nov 2001 15:13:36 -0000 Message-ID: <3BEFE71D.1BA32DB6@cygnus.com> Date: Mon, 01 Oct 2001 08:25:00 -0000 From: Fernando Nasser Organization: Red Hat , Inc. - Toronto X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-12smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Grant Edwards CC: insight@sources.redhat.com, Keith Seitz Subject: Re: No step button using insight w/ remote target. References: <20011107172319.A2924@visi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2001-q4/txt/msg00001.txt.bz2 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fernando Nasser To: Grant Edwards Cc: insight@sources.redhat.com, Keith Seitz Subject: Re: No step button using insight w/ remote target. Date: Mon, 12 Nov 2001 07:13:00 -0000 Message-ID: <3BEFE71D.1BA32DB6@cygnus.com> References: <20011107172319.A2924@visi.com> X-SW-Source: 2001-q4/msg00302.html Message-ID: <20011112071300.01gV4XXdWi4nDx1wb1SgDjiYTznk_ARnB_kFHTVHjmA@z> 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