From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31218 invoked by alias); 2 Mar 2003 08:26:02 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 31204 invoked by uid 71); 2 Mar 2003 08:26:01 -0000 Date: Sun, 02 Mar 2003 08:26:00 -0000 Message-ID: <20030302082601.31203.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Eric R. Krause" Subject: Re: target/5563: [Cygwin] using a pointer named "end" consistently produces segfault in windows. Reply-To: "Eric R. Krause" X-SW-Source: 2003-03/txt/msg00034.txt.bz2 List-Id: The following reply was made to PR target/5563; it has been noted by GNATS. From: "Eric R. Krause" To: , , , , Cc: Subject: Re: target/5563: [Cygwin] using a pointer named "end" consistently produces segfault in windows. Date: Sun, 2 Mar 2003 03:19:30 -0500 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