This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: target/5563: [Cygwin] using a pointer named "end" consistently produces segfault in windows.
- From: "Eric R. Krause" <ekraus02 at baker dot edu>
- To: <gcc-gnats at gcc dot gnu dot org>, <gcc-bugs at gcc dot gnu dot org>, <arlankfo at 141 dot com>, <nobody at gcc dot gnu dot org>, <gcc-prs at gcc dot gnu dot org>
- Date: Sun, 2 Mar 2003 03:19:30 -0500
- Subject: Re: target/5563: [Cygwin] using a pointer named "end" consistently produces segfault in windows.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
r=5563
Confirmed for gcc 2.95.3/cygwin, also for gcc 3.2 cygwin package,
on Windows 2000. Microsoft Visual C++ 6.0-compiled executable of
same code does not segfault, nor does gcc on Debian GNU/Linux with
gcc-2.95 package version 2.95.4-11woody1.
The obvious workaround is not to use 'end' as a variable name. Also,
initializing the global 'end' variable causes the test program to
run OK, as does declaring the 'end' variable as being 'static'.
---
Eric R. Krause