From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Deephanphongs To: gdb-patches@sources.redhat.com Subject: Re: [PATCH] specify arguments to debugee from commandline (second try) Date: Wed, 11 Apr 2001 19:05:00 -0000 Message-id: <20010411221401.A3294@llamedos.org> References: <20010330163603.A27435@llamedos.org> <20010403013600.B7630@llamedos.org> <87n19uirbk.fsf@creche.redhat.com> <200104060832.EAA17613@indy.delorie.com> <87vgoi58lr.fsf@creche.redhat.com> <200104061626.MAA01438@indy.delorie.com> <87ofu96gop.fsf@creche.redhat.com> <200104062013.QAA11798@indy.delorie.com> <20010411013553.B2397@llamedos.org> <200104110855.EAA32225@delorie.com> X-SW-Source: 2001-04/msg00116.html Thus spake Eli Zaretskii (eliz@delorie.com): > > From: David Deephanphongs > > > > > > 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. Dave -- - "You pay for it before you eat it? What happens if it's dreadful?" - "That's why." -- (Terry Pratchett, Moving Pictures)