Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Fabian Cenedese <Cenedese@indel.ch>
To: gdb@sourceware.org
Subject: Re: Path problem with dwarf on cygwin
Date: Wed, 29 Nov 2006 16:12:00 -0000	[thread overview]
Message-ID: <5.2.0.9.1.20061129170904.0187d850@NT_SERVER> (raw)
In-Reply-To: <20061129154258.GA1999@nevyn.them.org>

At 10:42 29.11.2006 -0500, Daniel Jacobowitz wrote:
>On Wed, Nov 29, 2006 at 04:38:41PM +0100, Fabian Cenedese wrote:
>> How can this happen? Is this a problem of gcc or gdb? As I call gcc directly,
>> not from inside the cygwin shell, I give all paths with backslashes. So why is
>> there one with a forward slash?
>> 
>> Is there a possibility to tell gdb that these are the same files and not
>> create two symtabs? Or maybe a flag for configure of gcc/gdb? Something
>> like the textmode.o module for cygwin compiled programs.
>
>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.

But apparently this only affects dwarf info, is that correct? Can I
work around this by supplying pathes with all forward slashes?

Thanks

bye  Fabi



  reply	other threads:[~2006-11-29 16:12 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 [this message]
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

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=5.2.0.9.1.20061129170904.0187d850@NT_SERVER \
    --to=cenedese@indel.ch \
    --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