[Bug server/28392] gdb server no longer supports argument globbing and variable substitution

["m.weghorn at posteo dot de" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=28392

--- Comment #7 from Michael Weghorn <m.weghorn at posteo dot de> ---
> I would probably lean towards option 1:
> 
>  - GDB has worked this way for a while, and it would probably break the
> workflow of more users than changing gdbserver
>  - Given the examples above, I think the GDB behavior is somewhat sane
>  - The "new" gdbserver behavior is now released in the wild, in gdbserver
> 11.1 (IIUC).  And it's what is in master today.  We could always revert to
> the old behavior as a "bug fix" in gdbserver 11.2, but that might end up
> even more confusing.  So where we are standing today, we can see the change
> in gdbserver's behavior as being on purpose (to align gdbserver's behavior
> with gdb's), but add --no-escape-args to provide an escape hatch.
> 
> There would be a third option, to revert gdbserver's behavior to be
> different than gdb's, and add an --escape-args switch.  But I don't really
> like that, as that makes gdb and gdbserver behave differently, whereas we
> try to make the two converge.

Thanks a lot for you input.
Unless I completely misunderstand something, I'd read that as being in favour
of what I tried to describe as option **2** in comment 5, though, right? (not
option 1)

If so, I'll try to come up with patches to implement that.

-- 
You are receiving this mail because:
You are on the CC list for the bug.