From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6315 invoked by alias); 22 Feb 2006 19:28:51 -0000 Received: (qmail 6207 invoked by uid 22791); 22 Feb 2006 19:28:49 -0000 X-Spam-Check-By: sourceware.org Received: from gandalf.inter.net.il (HELO gandalf.inter.net.il) (192.114.186.17) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 22 Feb 2006 19:28:48 +0000 Received: from nitzan.inter.net.il (nitzan.inter.net.il [192.114.186.20]) by gandalf.inter.net.il (MOS 3.7.1-GA) with ESMTP id HYM03202; Wed, 22 Feb 2006 21:26:15 +0200 (IST) Received: from HOME-C4E4A596F7 (IGLD-83-130-205-93.inter.net.il [83.130.205.93]) by nitzan.inter.net.il (MOS 3.7.3-GA) with ESMTP id CTN22687 (AUTH halo1); Wed, 22 Feb 2006 21:26:09 +0200 (IST) Date: Wed, 22 Feb 2006 19:34:00 -0000 Message-Id: From: Eli Zaretskii To: gdb@sourceware.org CC: jimb@red-bean.com In-reply-to: <20060222142953.GA20393@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 22 Feb 2006 09:29:53 -0500) Subject: Re: Quoting, backslashes, CLI and MI Reply-to: Eli Zaretskii References: <20060221213324.GA30729@nevyn.them.org> <8f2776cb0602212223p1b8fda93meb9b12e5d187b3b6@mail.gmail.com> <20060222142953.GA20393@nevyn.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-02/txt/msg00304.txt.bz2 > Date: Wed, 22 Feb 2006 09:29:53 -0500 > From: Daniel Jacobowitz > Cc: gdb@sourceware.org > > -exec-arguments ARGS; should it take a single string which is then > split by buildargv into a vector, or should it take freeform text which > is then split into an argument vector? Well, right now it takes a > literal string, since it just passes the text to CLI "set args". > That's saved as a string and then passed to create_inferior as a > string, and eventually passed directly to a shell in the fork-child.c > case. So, as un-MI-like as it is, I think I'd have to leave this one > alone for now - it's just too big a can of worms! We should leave it alone, and not only because it's a mess: "-exec-arguments" _should_ pass its argument to the shell, it should not second-guess the shell features, nor reinvent them.