Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: qinwei@sunnorth.com.cn, bjgnu@sunnorth.com.cn,
		gdb-patches@sourceware.org
Subject: Re: [Patch]: Path problems when setting breakpoints using  mingw-build-gdb
Date: Tue, 06 Feb 2007 11:58:00 -0000	[thread overview]
Message-ID: <20070206115756.GA28356@nevyn.them.org> (raw)
In-Reply-To: <uodo7zzel.fsf@gnu.org>

On Tue, Feb 06, 2007 at 06:24:34AM +0200, Eli Zaretskii wrote:
> > Date: Mon, 5 Feb 2007 07:06:17 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Eli Zaretskii <eliz@gnu.org>, bjgnu@sunnorth.com.cn,
> > 	gdb-patches@sourceware.org
> > 
> > What I believe we need to do is use a different function to
> > compare filenames, one which allows \ and / to be treated as equal (on
> > all platforms).  I don't know if it should also do case insensitive
> > comparison on all platforms, but it should certainly do so on Windows.
> 
> We already have FILENAME_CMP; perhaps all we need is to expand it on
> Windows into a specially written (perhaps inline) function instead of
> strcasecmp.
> 
> WDYT?

On all platforms, please, not just on Windows.  I regularly use Linux
debuggers with files compiled on Windows, that contain backslashes - I
would love to make that work better.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-02-06 11:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-03  2:33 秦巍
2007-02-03 11:26 ` Eli Zaretskii
2007-02-05  8:37   ` 秦巍
2007-02-05 12:06     ` Daniel Jacobowitz
2007-02-06  4:24       ` Eli Zaretskii
2007-02-06 11:58         ` Daniel Jacobowitz [this message]
2007-02-07 18:12           ` Eli Zaretskii
2007-02-07 18:37             ` Daniel Jacobowitz

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=20070206115756.GA28356@nevyn.them.org \
    --to=drow@false.org \
    --cc=bjgnu@sunnorth.com.cn \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=qinwei@sunnorth.com.cn \
    /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