Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Cenedese@indel.ch, gdb@sourceware.org
Subject: Re: Path problem with dwarf on cygwin
Date: Wed, 29 Nov 2006 19:05:00 -0000	[thread overview]
Message-ID: <20061129190506.GA9754@nevyn.them.org> (raw)
In-Reply-To: <upsb6ayi8.fsf@gnu.org>

On Wed, Nov 29, 2006 at 08:39:11PM +0200, Eli Zaretskii wrote:
> > Date: Wed, 29 Nov 2006 10:42:58 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: gdb@sourceware.org
> > 
> > I said a couple of weeks ago that I had a really nasty patch for this
> > problem, but never got around to cleaning it up.  You've built a Cygwin
> > GDB, therefore when it needs to construct a path, it uses forward
> > slashes.  Yet your debugging info matches what you gave the compiler,
> > i.e. has backwards slashes.  The debugger needs to be taught smarter
> > filename comparison.
> 
> Why ``nasty''?  Isn't it enough to modify the FILENAME_CMP macro, and
> be done with that?  If not, what else need to be changed, and why?

I didn't say that the proper solution was nasty, just that my first
version of the code was :-)  It won't be hard to clean up, if I can
find the time.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2006-11-29 19:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29 15:40 Fabian Cenedese
2006-11-29 15:43 ` Daniel Jacobowitz
2006-11-29 16:12   ` Fabian Cenedese
2006-11-29 16:13     ` Daniel Jacobowitz
2006-11-29 16:24       ` Fabian Cenedese
2006-11-29 18:39   ` Eli Zaretskii
2006-11-29 19:05     ` Daniel Jacobowitz [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=20061129190506.GA9754@nevyn.them.org \
    --to=drow@false.org \
    --cc=Cenedese@indel.ch \
    --cc=eliz@gnu.org \
    --cc=gdb@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