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

Jan Kratochvil
2011-12-05T20:16:30Z

On Sun, 04 Dec 2011 03:55:07 +0100, Doug Evans wrote:
> Poorly chosen names lead to confusion, bugs, and wasted time.
> [No claim is made that this is news. :-)]

Just $use_gdb_stub is a different form of [target_info exists use_gdb_stub] so
no matter what the name is IMO it is correct the name is the same.

And one cannot change use_gdb_stub in the board file for board files backward
compatibility.

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

It does not work with non-extended gdbserver - which has use_gdb_stub == 1.
Also my change did not change it:
- if [target_info exists use_gdb_stub] {
+ if $use_gdb_stub {
(gdb) target remote localhost:1234
Remote debugging using localhost:1234
[...]
(gdb) start
The "remote" target does not support "run". Try "help target" or "continue".

It works with extended gdbserver - which has use_gdb_stub == 0.

I do not see the problem you describe.

Thanks,
Jan