From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13463 invoked by alias); 8 May 2003 09:03:00 -0000 Mailing-List: contact insight-prs-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-prs-owner@sources.redhat.com Received: (qmail 13448 invoked by uid 71); 8 May 2003 09:03:00 -0000 Resent-Date: 8 May 2003 09:03:00 -0000 Resent-Message-ID: <20030508090300.13447.qmail@sources.redhat.com> Resent-From: insight-gnats@sources.redhat.com (GNATS Filer) Resent-Cc: insight-prs@sources.redhat.com Resent-Reply-To: insight-gnats@sources.redhat.com, richard.vanwegen@priorsep.com Received: (qmail 13383 invoked by uid 48); 8 May 2003 09:02:49 -0000 Message-Id: <20030508090249.13382.qmail@sources.redhat.com> Date: Thu, 08 May 2003 09:03:00 -0000 From: richard.vanwegen@priorsep.com Reply-To: richard.vanwegen@priorsep.com To: insight-gnats@sources.redhat.com X-Send-Pr-Version: gnatsweb-2.9.3 (1.1.1.1.2.31) Subject: insight/227: Doesn't find source code files in directories with a space in the name X-SW-Source: 2003-q2/txt/msg00016.txt.bz2 List-Id: >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: