From: Yao Qi <yao@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Skip gcore-buffer-overflow.exp on windows
Date: Mon, 19 Nov 2012 02:41:00 -0000 [thread overview]
Message-ID: <50A99C25.50100@codesourcery.com> (raw)
In-Reply-To: <83pq3d4k3c.fsf@gnu.org>
On 11/16/2012 11:56 PM, Eli Zaretskii wrote:
> This is still less than 256 characters, so I don't understand why it
> fails. And you can make it even less if you use relative file names.
My experiments show that the max length of file name is 241.
$ i686-pc-linux-gnu-gcc.exe gcore-buffer-overflow.c -g -lm -o
gcore-buffer-overflow111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111222222222222222222222222222223567
We'll get the error when file name length is 242.
$ i686-pc-linux-gnu-gcc.exe gcore-buffer-overflow.c -g -lm -o
gcore-buffer-overflow1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111112222222222222222222222222222235678
c:/cygwin/home/yqi/test-i686-mingw32/test-build5-lucid-cs/ia32-2012.09/bin/../lib/gcc/i686-pc-linux-gnu/4.7.2/../../../../i686-pc-linux-gnu/bin/ld.exe:
cannot open output file
gcore-buffer-overflow1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111112222222222222222222222222222235678:
No such file or directory
and I checked that 'fopen' can't open the file whose length exceeds 241.
However, I can 'cp' or 'mv' file to the file with long file name (242
~ 256).. Any ideas?
--
Yao (é½å°§)
prev parent reply other threads:[~2012-11-19 2:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 15:02 Yao Qi
2012-11-15 15:21 ` Joel Brobecker
2012-11-15 16:04 ` Pedro Alves
2012-11-15 17:09 ` Eli Zaretskii
2012-11-16 1:11 ` Yao Qi
2012-11-16 15:57 ` Eli Zaretskii
2012-11-19 2:41 ` Yao Qi [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=50A99C25.50100@codesourcery.com \
--to=yao@codesourcery.com \
--cc=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