Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: ???? <qinwei@sunnorth.com.cn>
Cc: Eli Zaretskii <eliz@gnu.org>,
	bjgnu@sunnorth.com.cn, 	gdb-patches@sourceware.org
Subject: Re: [Patch]: Path problems when setting breakpoints using  mingw-build-gdb
Date: Mon, 05 Feb 2007 12:06:00 -0000	[thread overview]
Message-ID: <20070205120616.GA25602@nevyn.them.org> (raw)
In-Reply-To: <OF809B3630.62AFBC9A-ON48257279.0027D6A9-48257279.002F2282@sunnorth.com.cn>

On Mon, Feb 05, 2007 at 04:34:50PM +0800, ???? wrote:
> Secondly, "start_subfile" is called according to .debug_line's
> "Directory Table" and "File Name Table":
> 
> gdb will use "SLASH_STRING" to combine full filenames, and create
> another subfile, we call it subfile2
> (gdb) p *subfile2
> $89 = {
>   next = 0x8961f40, 
>   name = 0x89623a0 "F:\\gcd\\2310gcd/main.c", 
>   dirname = 0x89623c0 "F:\\\\gcd\\\\2310gcd", 
>   line_vector = 0x0, 
>   line_vector_length = 0, 
>   language = language_c, 
>   debugformat = 0x0
> }
> 
> subfile1->name and subfile2->name are not equal.

Right.  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.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-02-05 12:06 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 [this message]
2007-02-06  4:24       ` Eli Zaretskii
2007-02-06 11:58         ` Daniel Jacobowitz
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=20070205120616.GA25602@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