This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH] specify arguments to debugee from commandline (second try)
Thus spake Eli Zaretskii (firstname.lastname@example.org):
> > From: David Deephanphongs <email@example.com>
> > I'm not convinced that we want to support any special handling...
> > We could force the user to just escape everything appropriately:
> > If they want equivalent to:
> > set args "this is a" test
> > force them to do:
> > gdb echo -- \"this is a\" test
> But that's exactly what Tom was trying to avoid! His intent was to
> allow substitution of "gdb COMMAND --run ARGS" for each case of
> "COMMAND ARGS" in a mechanical way, which means ARGS should not be
> modified in any way.
I'm still not convinced that it's appropriate for /gdb/ to do the
escaping - if it's being put into a script, it's much easier to do
it in perl than C..
What characters need to be escaped, anyway? It seems like it much
differ from shell to shell.
- "You pay for it before you eat it? What happens if it's dreadful?"
- "That's why."
-- (Terry Pratchett, Moving Pictures)