Re: target/5563: [Cygwin] using a pointer named "end" consistently produces segfault in windows.

Re: target/5563: [Cygwin] using a pointer named "end" consistently produces segfault in windows.

[giovannibajo]

Synopsis: [Cygwin] using a pointer named "end" consistently produces segfault in windows.

State-Changed-From-To: open->closed
State-Changed-By: bajo
State-Changed-When: Sat May 17 06:53:28 2003
State-Changed-Why:
    Not a GCC bug, and already fixed in binutils.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5563

Re: target/5563: [Cygwin] using a pointer named "end" consistently produces segfault in windows.

[Danny Smith]

The following reply was made to PR target/5563; it has been noted by GNATS.

From: Danny Smith <dannysmith@clear.net.nz>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, arlankfo@141.com,
 nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org
Cc:  
Subject: Re: target/5563: [Cygwin] using a pointer named "end" consistently
 produces segfault in windows.
Date: Mon, 03 Mar 2003 02:44:11 +0000

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=g
 cc&pr=5563
 
 Fixed by this patch to binutils:
 
 CVSROOT: /cvs/uberbaum
 Module name: ld
 Changes by: cgf at sourceware dot org 2003-03-03 02:38:10
 
 Modified files:
  .              : ChangeLog
  scripttempl    : pe.sc
 
 Log message:
  * scripttempl/pe.sc: Use PROVIDE with etext, end, _end,
 
 Patches:
 http://sources.redhat.com/cgi-bin/cvsweb.cgi/ld/ChangeLog.diff?cvsroot=u
 berbaum&r1=1.872&r2=1.873
 http://sources.redhat.com/cgi-bin/cvsweb.cgi/ld/scripttempl/pe.sc.diff?c
 vsroot=uberbaum&r1=1.7&r2=1.8
 
 
 
 

Re: target/5563: [Cygwin] using a pointer named "end" consistently produces segfault in windows.

[Danny Smith]

The following reply was made to PR target/5563; it has been noted by GNATS.

From: Danny Smith <dannysmith@clear.net.nz>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, arlankfo@141.com,
 nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org
Cc:  
Subject: Re: target/5563: [Cygwin] using a pointer named "end" consistently
 produces segfault in windows.
Date: Sun, 02 Mar 2003 09:52:10 +0000

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=g
 cc&pr=5563
 
 This is really a binutils problem isn't it.  In  ld/scripttempl/pe/sc,
 line 132ff
 
   .endjunk ${RELOCATING+BLOCK(__section_alignment__)} :
   {
     /* end is deprecated, don't use it */
     ${RELOCATING+ end = .;}
     ${RELOCATING+ _end = .;}
     ${RELOCATING+ __end__ = .;}
   }
 
 Danny
 

Re: target/5563: [Cygwin] using a pointer named "end" consistently produces segfault in windows.

[Eric R. Krause]

The following reply was made to PR target/5563; it has been noted by GNATS.

From: "Eric R. Krause" <ekraus02@baker.edu>
To: <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <arlankfo@141.com>,
        <nobody@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>
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