This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: gdb/535: GDB will not open symbol files if there is a space inthe filename or path
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 21 May 2002 06:58:02 -0000
- Subject: Re: gdb/535: GDB will not open symbol files if there is a space inthe filename or path
- Reply-to: Andrew Cagney <ac131313 at cygnus dot com>
The following reply was made to PR gdb/535; it has been noted by GNATS.
From: Andrew Cagney <ac131313@cygnus.com>
To: nobody@sources.redhat.com, gdb-gnats@sources.redhat.com,
gdb-prs@sources.redhat.com
Cc:
Subject: Re: gdb/535: GDB will not open symbol files if there is a space in
the filename or path
Date: Tue, 21 May 2002 02:48:13 -0400
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=535
Hello,
Thanks for the bug report!
In terms of fixing this, there are a number of problems:
- the filename_completer() will need to escape space characters as part
of a completion:
(gdb) load /tmp/abc def
vs
(gdb) load /tmp/abc\ def
- there should be a function that all of GDB uses to parse a file name.
The code behind the function buildargv() might serve as a good starting
point.
- more generally, GDB's CLI needs to gain a stronger syntax. There are
many other places where a space can make a difference. The disassembler
for instance, treats:
disassemble a +4
and
disassemble a+4
differently.
Andrew