From: Eli Zaretskii <eliz@gnu.org>
To: "Michael Fischer" <fischermi@t-online.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] source.s: Fix problem handling windows like path with MinGW
Date: Sat, 17 Jun 2006 19:45:00 -0000 [thread overview]
Message-ID: <ur71n36sm.fsf@gnu.org> (raw)
In-Reply-To: <JLEAKDMELBINENLADICFKEFECIAA.fischermi@t-online.de>
> From: "Michael Fischer" <fischermi@t-online.de>
> Date: Sat, 17 Jun 2006 18:23:23 +0200
>
> the patch below will fix the problem if an application sends path
> information like "d:\foo1\foo2" instead of "/d/foo1/foo2"
Thank you for your contribution.
However, I'm not sure I understand the details and/or the motivation.
The patch is MinGW-specific, so I'd expect the source path to use `;',
not `:', to separate directories. That is what I see in my
MinGW-compiled GDB (built for native Windows debugging).
In other words, DIRNAME_SEPARATOR is supposed to be `;' in this
build. Can you explain how it became `:'?
> Here are some examples how the path could look like:
>
> 1. "D:\Projekte\Eclipse\Test:$cwd"
> 2. "D:\Projekte\Eclipse\Test:D:\Projekte\Eclipse\Test\src:D:\Projekte\Eclipse\Test\inc:$cwd"
If you want GDB to distinguish between the two different uses of `:',
then I think we shouldn't even try. While it's probable that in
"d:\foo:c:\bar" the 1st and the 3rd colon are not separators but parts
of the drive letter, nothing prevents a user from legitimately using
it in a non-probable way, i.e. the user could really mean to search
the directories `d', `\foo', `c', and `\bar'. GDB has no business
second-guessing the user's intent, IMHO.
The solution to this, IMO, is to make sure your GDB uses `;' to
separate directories in paths.
prev parent reply other threads:[~2006-06-17 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 16:23 Michael Fischer
2006-06-17 19:45 ` Eli Zaretskii [this message]
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=ur71n36sm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=fischermi@t-online.de \
--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