Re: ping: Re: [patch] Forbid "run" etc. for use_gdb_stub targets

Doug Evans
2011-12-04T02:55:22Z

On Sat, Dec 3, 2011 at 5:29 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Sun, 04 Dec 2011 02:02:06 +0100, Doug Evans wrote:
>> I'd like to get away from conflating anything related to gdb stubs and
>> valgrind / gdbserver.
>
> Currently $use_gdb_stub means the startup has been already executed when the
> testsuite gets into GDB control.
>
> IIUC in reality currently the real stubs are not in use but gdbserver in
> non-extended mode behaves as native GDB with the stubs in the past.

Not precisely.

> Maybe $use_gdb_stub name is not fortunate for what it does, real stubs are
> only subset of $use_gdb_stub cases.

Poorly chosen names lead to confusion, bugs, and wasted time.
[No claim is made that this is news. :-)]

Plus, there's no reason why, for example, gdb_start_cmd can't work
with target remote and gdbserver.