From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keith Seitz To: Grant Edwards Cc: Subject: Re: No step button using insight w/ remote target. Date: Mon, 19 Nov 2001 12:00:00 -0000 Message-ID: References: <20011107172319.A2924@visi.com> X-SW-Source: 2001-q4/msg00330.html Message-ID: <20011119120000.PapiEQv7elz5fK8SM8IiZQhdQbZ_lbLZ6tV1NUkO2NE@z> On Wed, 7 Nov 2001, Grant Edwards wrote: > 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. Hmm.. I cannot imagine why this happens. Is the baudrate set? If you're on windows, you might try lowering the remote timeout. By default, it is set to some fairly normal number, like 30. But as I recall (maybe incorrectly now), the real timeout was HUGE on cygwin. Try setting it to something like 1 and see if it at least times out. > 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. This is usually symptomatic of pid/ptid problems in gdb. When your attached (and the Control items on the toolbar are disabled), what do the following commands return? (In Insight's console window) (gdb) tk set ::gdb_running (gdb) tk gdb_target_has_execution Keith