From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Skip gcore-buffer-overflow.exp on windows
Date: Thu, 15 Nov 2012 17:09:00 -0000 [thread overview]
Message-ID: <83k3tmu71a.fsf@gnu.org> (raw)
In-Reply-To: <1352991707-29104-1-git-send-email-yao@codesourcery.com>
> From: Yao Qi <yao@codesourcery.com>
> Date: Thu, 15 Nov 2012 23:01:47 +0800
>
> Hi,
> When running gcore-buffer-overflow.exp on ia32/windows host,
> we saw the following error,
>
> cp: accessing `XXX/gdb.base/gcore-buffer-overflow-01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789': File name too long
>
> Looks we don't have other supported hosts that have file name length
> limitation, so this patch simply skips it on windows. Is it OK?
??? First, does the MinGW build of GDB really support the gcore
command? In my testing, it fails saying "Can't create a corefile".
Which figures, since MinGW doesn't support them.
And second, why in the world is this file name too long? The
limitation imposed by Windows on file-names used in "ANSI" APIs is 256
characters, not 80 or 150 that we see above. So why is this failing?
Apologies if I'm missing something.
next prev parent reply other threads:[~2012-11-15 17:09 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 [this message]
2012-11-16 1:11 ` Yao Qi
2012-11-16 15:57 ` Eli Zaretskii
2012-11-19 2:41 ` 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=83k3tmu71a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.com \
/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