From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28734 invoked by alias); 11 Aug 2006 13:48:59 -0000 Received: (qmail 28726 invoked by uid 22791); 11 Aug 2006 13:48:59 -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; Fri, 11 Aug 2006 13:48:49 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1GBXNT-00059O-Me; Fri, 11 Aug 2006 09:48:43 -0400 Date: Fri, 11 Aug 2006 13:48:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: Nikolay.Molchanov@Sun.COM, gdb@sourceware.org Subject: Re: How to set a breakpoint in file, which name has spaces? Message-ID: <20060811134842.GA19749@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , Nikolay.Molchanov@Sun.COM, gdb@sourceware.org References: <44D8E404.5050407@Sun.COM> <44D98D66.9060202@sun.com> <44DAD087.30004@sun.com> <20060810125827.GA18306@nevyn.them.org> <44DB6093.4030905@sun.com> <20060810175119.GA26275@nevyn.them.org> <44DC151F.3030009@sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11+cvs20060403 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-08/txt/msg00102.txt.bz2 On Fri, Aug 11, 2006 at 03:55:40PM +0300, Eli Zaretskii wrote: > > Date: Thu, 10 Aug 2006 22:26:55 -0700 > > From: Nikolay Molchanov > > Cc: gdb@sourceware.org > > > > I hope we will never need to set a breakpoint in a file, > > which name has double quotes :-) > > MS-Windows filesystems don't allow file names with double quotes, so > you needn't worry about that. > > Daniel, should we update the manual in some way, or is this a bug that > should be fixed? That's a good question :-) This all comes down to decode_line_1. The question of whether to change its parsing or document its quirks is beyond me, I'm afraid. I'm reluctant to try touching that code. I wonder if, for some major version bump, we should document a new syntax for referring to source locations and implement it from scratch? -- Daniel Jacobowitz CodeSourcery