From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28904 invoked by alias); 8 Jul 2009 17:43:24 -0000 Received: (qmail 28883 invoked by uid 22791); 8 Jul 2009 17:43:22 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 08 Jul 2009 17:43:16 +0000 Received: (qmail 17574 invoked from network); 8 Jul 2009 17:43:14 -0000 Received: from unknown (HELO orlando) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 8 Jul 2009 17:43:14 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: How to fix solib path name? Date: Wed, 08 Jul 2009 18:30:00 -0000 User-Agent: KMail/1.9.10 Cc: Aleksandar Ristovski , gdb-patches@sources.redhat.com References: <1247063678.3870.59.camel@pavilion> <200907081649.41971.pedro@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <200907081843.17373.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-07/txt/msg00268.txt.bz2 Message-ID: <20090708183000.URWo7zLN4doK2MRjcWfhbDD8m5zGTPe015QLRviyc7g@z> On Wednesday 08 July 2009 18:15:05, Aleksandar Ristovski wrote: > Finally, we don't have the issue of fwd/backward slashes, > but I think it could be fixed in Danny's case by configuring > gdb to define HAVE_DOS_BASED_FILE_SYSTEM, Defines/macros influencing GDB's view of the *target* are bad (TM). :-/ > or by taking care > of it in find_and_open_solib. Windows targets use solib-target.c, pretty much agnostic of Windows, really. CE's version of explorer doesn't allow creating files with '/' slashes --- it claims it's an invalid character for a filename. Not so sure if it's allowed at the filesystem or win32 api levels though. We could just punt and make gdbserver do the translation. We already do it when creating a process (win32-low.c:create_process). BTW, IIRC, CE doesn't have notion of drive letters either ("c:", "d:"), it has a single rooted filesystem. Yay for something MSFT did right! Then there's case sensitivity as well (which could be considered a filesystem, not target property) ... I hope that the OS is reporting the filename exactly as as seen on the filesystem --- which is what I've been seeing so far. I think that with other Windows versions we have a problem here. -- Pedro Alves