From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: Keith Seitz <keiths@redhat.com>,
gdb@sourceware.org,
MinGW Users List <mingw-users@lists.sourceforge.net>
Subject: Re: setting a breakpoint on a dll, relative path or absolute path issue
Date: Sun, 12 Jun 2011 07:56:00 -0000 [thread overview]
Message-ID: <20110612075630.GA9347@host1.jankratochvil.net> (raw)
In-Reply-To: <4DF46F19.1020009@gmail.com>
On Sun, 12 Jun 2011 09:47:37 +0200, asmwarrior wrote:
> 1, either we should store the
> "E:/code/cb/wx/wxWidgets-2.8.12/src/common/datetime.cpp"
> instead of
> "E:\code\cb\wx\wxWidgets-2.8.12\build\msw/../../src/common/datetime.cpp"
> in the symbol tables.
This does not work, the paths are not the same:
$ mkdir dir dir/subdir; echo file >dir/file; ln -s dir/subdir symlink; cat symlink/../file file
file
cat: file: No such file or directory
And one of the MinGW principles is to keep the backslashed names (\), not to
translate them to slashed ones (/) like CygWin does.
Regards,
Jan
next prev parent reply other threads:[~2011-06-12 7:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 7:49 asmwarrior
2011-06-11 17:56 ` Keith Seitz
2011-06-12 3:56 ` asmwarrior
2011-06-12 7:45 ` asmwarrior
2011-06-12 7:56 ` Jan Kratochvil [this message]
2011-06-12 8:06 ` asmwarrior
2011-06-12 16:22 ` [Mingw-users] " Earnie
2011-06-12 16:51 ` Eli Zaretskii
2011-06-12 16:54 ` Jan Kratochvil
[not found] ` <4DF37ADA.3070905@users.sourceforge.net>
2011-06-12 8:15 ` asmwarrior
[not found] ` <4DF4513A.3090902__7466.60719528354$1307866544$gmane$org@gmail.com>
2011-06-13 6:33 ` Asm warrior
2011-06-13 17:02 ` Eli Zaretskii
2011-06-14 3:14 ` Asm warrior
2011-06-14 3:49 ` Asm warrior
2011-06-14 4:22 ` Jeffrey Walton
2011-06-14 5:27 ` setting a breakpoint on a dll, relative path or absolute path issue[solved with a patch] asmwarrior
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=20110612075630.GA9347@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=asmwarrior@gmail.com \
--cc=gdb@sourceware.org \
--cc=keiths@redhat.com \
--cc=mingw-users@lists.sourceforge.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).