From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix cygwin compilation failure due to nameless LOAD_DLL_DEBUG_EVENT causes ntdll.dll to be missing
Date: Wed, 18 Dec 2013 20:01:00 -0000 [thread overview]
Message-ID: <83y53iapy6.fsf@gnu.org> (raw)
In-Reply-To: <20131218191757.GC30010@calimero.vinschen.de>
> Date: Wed, 18 Dec 2013 20:17:57 +0100
> From: Corinna Vinschen <vinschen@redhat.com>
>
> > > I don't know, but I doubt it. The filenames in case of calling the
> > > _wfopen functions are probably sent directly to the underlying WIn32
> > > functions.
> >
> > I don't think they can do that, because it would mean that relative
> > file names, "../foo", etc. are forbidden for _wfopen. The CRT
> > functions must go through file-name normalization, so unless they
> > detect \\?\ file names up front and refrain from any processing, the
> > long file names will not work, because the normalization routines are
> > where these limitations live, AFAIK.
>
> There's a lot of theory here. Did you actually *try* it?
No. Who can afford to try everything, unless they are paying you to
do that?
> I just did:
>
> ===========================================
> #include <stdio.h>
> #include <errno.h>
>
> int main(void)
> {
> FILE *fp;
>
> fp = _wfopen (L"\\\\?\\C:\\Windows\\System32\\ntdll.dll", L"r");
> if (!fp)
> printf ("_wfopen w/ long pathname fails, errno = %d\n", errno);
> else
> {
> printf ("_wfopen w/ long pathname works\n");
> fclose(fp);
> }
> return 0;
> }
> ===========================================
Thanks, that's good to know. But that's just one CRT function. There
are a gazillion of them, and I'm quite sure some use MAX_PATH of 260
internally. Just grep the sources of the CRT functions.
next prev parent reply other threads:[~2013-12-18 20:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52ab8d0e.8aa2420a.30ff.ffffd8f1SMTPIN_ADDED_BROKEN@mx.google.com>
2013-12-16 17:13 ` Pedro Alves
2013-12-16 22:50 ` Pierre Muller
2013-12-18 11:20 ` Corinna Vinschen
2013-12-18 15:46 ` Eli Zaretskii
2013-12-18 16:07 ` Corinna Vinschen
2013-12-18 17:03 ` Eli Zaretskii
2013-12-18 17:18 ` Corinna Vinschen
2013-12-18 17:29 ` Eli Zaretskii
2013-12-18 17:31 ` Corinna Vinschen
2013-12-18 18:19 ` Eli Zaretskii
2013-12-18 19:18 ` Corinna Vinschen
2013-12-18 20:01 ` Eli Zaretskii [this message]
2013-12-18 20:54 ` Corinna Vinschen
2013-12-19 18:33 ` Eli Zaretskii
2013-12-28 3:17 ` Joel Brobecker
2013-12-28 9:02 ` Eli Zaretskii
2013-12-13 22:41 Pierre Muller
2013-12-16 2:21 ` Yao Qi
2013-12-16 18:05 ` Pedro Alves
2013-12-17 0:43 ` Yao Qi
2013-12-17 8:43 ` Pierre Muller
2013-12-18 3:37 ` Yao Qi
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=83y53iapy6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).