public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: richard.vanwegen@priorsep.com
To: insight-gnats@sources.redhat.com
Subject: insight/227: Doesn't find source code files in directories with a space in the name
Date: Thu, 08 May 2003 09:03:00 -0000 [thread overview]
Message-ID: <20030508090249.13382.qmail@sources.redhat.com> (raw)
>Number: 227
>Category: insight
>Synopsis: Doesn't find source code files in directories with a space in the name
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu May 08 09:02:59 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: richard.vanwegen@priorsep.com
>Release: gdb 5.0 2003-03-03-CVS(cygwin special)
>Organization:
>Environment:
Windows ME, cygwin build
>Description:
If I load an .exe created from C++ source using GCC with DWARF2, and the sources files are located in a directory with a space in it, then Insight can't find the source files.
eg
c:/Eigene Dateien/CppSources/sourcefile1.cpp
If I move the source files to
c:/Eigene_Dateien/CppSources/sourcefile1.cpp
and recompile, the problem disappears.
The last cygwin build of Insight I used (GNU gdb 5.0 20001125-1) didn't have this problem.
It also seems to be impossible to add a path with a space to the list of directories to be searched for source files
(ie using the directory command)- the usual escape characters don't seem to work.
PS - yes, I know it's pretty stupid to have a path with a space in it. Blame Microsoft for calling the user's personal storage directory "My Documents".
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2003-05-08 9:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030508090249.13382.qmail@sources.redhat.com \
--to=richard.vanwegen@priorsep.com \
--cc=insight-gnats@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).