public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Eric R. Krause" <ekraus02@baker.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/5563: [Cygwin] using a pointer named "end" consistently produces segfault in windows.
Date: Sun, 02 Mar 2003 08:26:00 -0000	[thread overview]
Message-ID: <20030302082601.31203.qmail@sources.redhat.com> (raw)

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
 


             reply	other threads:[~2003-03-02  8:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-02  8:26 Eric R. Krause [this message]
2003-03-02  9:56 Danny Smith
2003-03-03  2:46 Danny Smith
2003-05-17  6:53 giovannibajo

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=20030302082601.31203.qmail@sources.redhat.com \
    --to=ekraus02@baker.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).