Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "Paul Derbyshire" To: cygwin@cygwin.com Date: Sat, 3 Aug 2002 00:09:58 -0400 MIME-Version: 1.0 Subject: Re: thread about Directory names containing spaces and G Reply-to: derbyshire@globalserve.net Message-ID: <3D4B1F56.3280.710CC70C@localhost> Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body On 2 Aug 2002 at 10:37, John Vincent wrote: > 1. try copying the executable to a directory with no spaces in the > path, and then try gdb to see if this makes a difference. Predictably, it works. > If the same problem remains after each step, I'd say that spaces > in the path were not the issue, and then another hypothesis will > need to be investigated. It doesn't remain after step 1. This is consistent with the other evidence that the executable itself is not the problem, and with the previous behavior of gdb with the executables in my system. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/