From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28383 invoked by alias); 19 May 2015 22:09:08 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 28373 invoked by uid 89); 19 May 2015 22:09:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 19 May 2015 22:09:07 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t4JM95Pp009685 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 19 May 2015 18:09:05 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t4JM93OQ029714; Tue, 19 May 2015 18:09:04 -0400 Message-ID: <555BB47E.9060500@redhat.com> Date: Tue, 19 May 2015 22:09:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Keith Seitz , Doug Evans CC: gdb-patches@sourceware.org Subject: Re: [PATCH v4 6/9] Explicit locations: introduce explicit locations References: <20150507180523.19629.77846.stgit@valrhona.uglyboxes.com> <20150507180559.19629.88488.stgit@valrhona.uglyboxes.com> <555A480B.9050200@redhat.com> In-Reply-To: <555A480B.9050200@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-05/txt/msg00503.txt.bz2 On 05/18/2015 09:14 PM, Keith Seitz wrote: > On 05/17/2015 11:12 PM, Doug Evans wrote: >> Not something to be done now, but just curious. >> Do we support source file names with spaces? > > Good question! My *guess* would be: it should! I certainly remember > fiddling with this, and explicit_location_lex_one does have handling for > it. [The lexer also allows quote-enclosed strings, just like linespec.] > > I just tested it (to be certain), and (survey says!): > > (gdb) fil ~/tmp/file\ with\ spaces > Reading symbols from ~/tmp/file with spaces...done. > (gdb) b -source file with spaces.c -line 4 Eh, do we handle files with spaces without requiring quoting anywhere else? The potential for ambiguity makes me a bit nervous to claim we support that. > Breakpoint 1 at 0x4004fa: file /home/keiths/tmp/file with spaces.c, line 4. > (gdb) r > Starting program: /home/keiths/tmp/file with spaces > > Breakpoint 1, main () at /home/keiths/tmp/file with spaces.c:4 > 4 return 1; > (gdb) > > ls-errs.exp exercises this a bit, too, albeit in a non-obvious way. Thanks, Pedro Alves