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: Pedro Alves <palves at redhat dot com>
- To: Keith Seitz <keiths at redhat dot com>, Doug Evans <xdje42 at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 19 May 2015 23:14:55 +0100
- 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> <555A480B dot 9050200 at redhat dot com> <555BB47E dot 9060500 at redhat dot com> <555BB53F dot 8040307 at redhat dot com>
On 05/19/2015 11:12 PM, Keith Seitz wrote:
> On 05/19/2015 03:09 PM, Pedro Alves wrote:
>
>>> (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.
>>
>
> The linespec parser doesn't normally require quoting:
>
> Reading symbols from ~/tmp/file with spaces...done.
> (gdb) b file with spaces.c:3
> Breakpoint 1 at 0x4004fa: file /home/keiths/tmp/file with spaces.c, line 3.
OK, as long as
b -source 'file with spaces -line 10' -line 20
works as expected (might be worth it of a test), the point is
moot then.
Thanks,
Pedro Alves