Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "Alex Song" To: Subject: gcc bug, cygwin specific cygwin-1.3.10-1 gcc-2.95.3-5 Date: Fri, 8 Mar 2002 17:03:26 +1000 Message-ID: <001301c1c66f$57e1cd50$1501010a@alexs> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Importance: Normal hi, i think i have found a bug, either that or i am very stupid. the bug is a gcc bug and it is cygwin specific (cygwin-1.3.10-1 gcc-2.95.3-5) and the following code causes a seg fault: ------------------------------------------- int end; int main () { end = 1; return 0; } -------------------------------------------- where as the following code does not: ------------------------------------------- int notend; int main () { notend = 1; return 0; } -------------------------------------------- it seems that the word "end" seems to do somethings differently. also if the variable was declared as static (static int end) there are not problems with that. hope you guys can help. cheers, alex ---------------------------------------------------------------------------- ---- Alex Song DESIGN ENGINEER EDMI Product Development Division alexs@pdd.edmi.com.au Ph : +61 7 3881 6443 FAX : +61 7 3881 6420 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/