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: Fri, 16 Nov 2012 15:57:00 -0000 [thread overview]
Message-ID: <83pq3d4k3c.fsf@gnu.org> (raw)
In-Reply-To: <50A592BB.1070403@codesourcery.com>
> Date: Fri, 16 Nov 2012 09:11:23 +0800
> From: Yao Qi <yao@codesourcery.com>
> CC: <gdb-patches@sourceware.org>
>
> On 11/16/2012 01:09 AM, Eli Zaretskii wrote:
> > ??? 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.
> >
>
> Eli,
> Our GDB is configured as "--host=i686-mingw32
> --target=i686-pc-linux-gnu", instead of native mingw32 gdb.
That explains one mystery, thanks.
> 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
> /scratch/yqi/i686-pc-linux-gnu-lite/obj/test-2012.09-999999-i686-pc-linux-gnu/host-i686-mingw32/default/gdb.d/gdb.base/gcore-buffer-overflow-01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789:
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.
So this mystery still stands.
next prev parent reply other threads:[~2012-11-16 15:57 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 [this message]
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=83pq3d4k3c.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