This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v4 6/9] Explicit locations: introduce explicit locations
- From: Keith Seitz <keiths at redhat dot com>
- To: Doug Evans <xdje42 at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 18 May 2015 13:14:03 -0700
- Subject: Re: [PATCH v4 6/9] Explicit locations: introduce explicit locations
- Authentication-results: sourceware.org; auth=none
- References: <20150507180523 dot 19629 dot 77846 dot stgit at valrhona dot uglyboxes dot com> <20150507180559 dot 19629 dot 88488 dot stgit at valrhona dot uglyboxes dot com> <m31tiequqq dot fsf at sspiff dot org>
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
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.
Keith