From: Eli Zaretskii <eliz@gnu.org>
To: 秦巍 <qinwei@sunnorth.com.cn>
Cc: gdb-patches@sourceware.org, bjgnu@sunnorth.com.cn
Subject: Re: [Patch]: Path problems when setting breakpoints using mingw-build-gdb
Date: Sat, 03 Feb 2007 11:26:00 -0000 [thread overview]
Message-ID: <uejp71nzl.fsf@gnu.org> (raw)
In-Reply-To: <OFBA6E1623.0870EACC-ON48257277.000DE389-48257277.000DFF3E@sunnorth.com.cn> (message from =?Big5?B?r7PE3g==?= on Sat, 3 Feb 2007 10:33:48 +0800)
> Cc: bjgnu@sunnorth.com.cn
> From: =?Big5?B?r7PE3g==?=<qinwei@sunnorth.com.cn>
> Date: Sat, 3 Feb 2007 10:33:48 +0800
>
> When using mingw-build-gdb on windows.
What is the GDB version you used? where did you get the binary?
> sending command "b main.c:3",
> gdb shows:
> No line 3 in file "F:\gcd\2310gcd\main.c".
> but sending command "b main",
> gdb shows:
> Breakpoint 1 at 0xa00011dc: file F:\gcd\2310gcd/main.c, line 3.
Could you please show a complete self-contained example, including the
source and the compilation command line? Also, please tell what
version of GCC you used. I'd like to try to reproduce this on my
machine.
> Maybe the defined SLASH_STRING is not correct on windows.
Did you try applying that patch, and if so, did the problem go away?
Personally, I don't think it's related at all, because SLASH_STRING
should not be used where an absolute file name is taken apart to look
for the directory and the basename. Instead, GDB should use other
macros, such as IS_DIR_SEPARATOR (from include/filenames.h), which do
cater to Windows filenames.
SLASH_STRING is only used to _construct_ file names, and that is okay,
since the Windows file I/O APIs recognize both \ and / as separators.
next prev parent reply other threads:[~2007-02-03 11:26 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 [this message]
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
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=uejp71nzl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bjgnu@sunnorth.com.cn \
--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