This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Skip gcore-buffer-overflow.exp on windows
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 15 Nov 2012 19:09:53 +0200
- Subject: Re: [PATCH] Skip gcore-buffer-overflow.exp on windows
- References: <1352991707-29104-1-git-send-email-yao@codesourcery.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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.