From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Aleksandar Ristovski <aristovski@qnx.com>,
gdb-patches@sources.redhat.com
Subject: Re: How to fix solib path name?
Date: Wed, 08 Jul 2009 18:24:00 -0000 [thread overview]
Message-ID: <200907081843.17373.pedro@codesourcery.com> (raw)
In-Reply-To: <h32k6q$qc1$1@ger.gmane.org>
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
WARNING: multiple messages have this Message-ID
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Aleksandar Ristovski <aristovski@qnx.com>,
gdb-patches@sources.redhat.com
Subject: Re: How to fix solib path name?
Date: Wed, 08 Jul 2009 18:30:00 -0000 [thread overview]
Message-ID: <200907081843.17373.pedro@codesourcery.com> (raw)
Message-ID: <20090708183000.URWo7zLN4doK2MRjcWfhbDD8m5zGTPe015QLRviyc7g@z> (raw)
In-Reply-To: <h32k6q$qc1$1@ger.gmane.org>
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
next prev parent reply other threads:[~2009-07-08 17:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 14:34 Danny Backx
2009-07-08 14:45 ` Aleksandar Ristovski
2009-07-08 14:51 ` Pedro Alves
2009-07-08 15:15 ` Aleksandar Ristovski
2009-07-08 15:21 ` Pedro Alves
2009-07-08 15:38 ` Aleksandar Ristovski
2009-07-08 15:49 ` Pedro Alves
2009-07-08 15:57 ` Pedro Alves
2009-07-08 17:19 ` Aleksandar Ristovski
2009-07-08 18:24 ` Pedro Alves [this message]
2009-07-08 18:30 ` Pedro Alves
2009-07-08 14:56 ` Pedro Alves
2009-07-08 15:07 ` Pedro Alves
2009-07-08 15:31 ` Danny Backx
2009-07-08 15:45 ` Pedro Alves
2009-07-08 15:45 ` Danny Backx
2009-07-08 16:19 ` Pedro Alves
2009-07-08 16:30 ` Danny Backx
2009-07-08 16:42 ` Pedro Alves
2009-07-08 17:15 ` Pedro Alves
2009-07-08 20:46 ` Danny Backx
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=200907081843.17373.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=aristovski@qnx.com \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb-patches@sourceware.org \
/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