From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10437 invoked by alias); 22 Feb 2006 04:35:31 -0000 Received: (qmail 10428 invoked by uid 22791); 22 Feb 2006 04:35:31 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 22 Feb 2006 04:35:29 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FBlip-0002jS-MW for gdb@sourceware.org; Tue, 21 Feb 2006 23:35:27 -0500 Date: Wed, 22 Feb 2006 05:24:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Subject: Re: Quoting, backslashes, CLI and MI Message-ID: <20060222043527.GA10442@nevyn.them.org> Mail-Followup-To: gdb@sourceware.org References: <20060221213324.GA30729@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i 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/msg00288.txt.bz2 On Wed, Feb 22, 2006 at 06:30:30AM +0200, Eli Zaretskii wrote: > > Date: Tue, 21 Feb 2006 16:33:24 -0500 > > From: Daniel Jacobowitz > > > > Prompted by some of Andrew's paths-with-spaces patches, and by another > > project I'm working on that had to add a var_filename set variable, > > I've been looking over the way GDB handles quoting of arguments. > > It's a mess. For most users this is not a big deal; the big losers > > are (A) pathnames with spaces in them, and (B) pathnames with backslashes in > > them, e.g. DJGPP and MinGW32 paths. > > Daniel, > > Thanks for a comprehensive summary. I will read it in depth and > respond by this evening; for now just one comment: the DJGPP port > assumes the user mostly uses forward slashes, not backslashes. > Perhaps doing that on Windows as well will make the job of fixing > what's broken easier. I don't think it's a bad limitation. Thanks; no rush on this - I'll find something else to keep me busy tomorrow and be back to it. I don't actually know which form of paths current Windows MI clients use. I agree that it would be convenient if they mostly used forward slashes; but it looks like Eclipse uses native backslashed paths primarily, so I've some interest in supporting them (to perturb Eclipse as little as possible). -- Daniel Jacobowitz CodeSourcery