This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 1.3.12: gcc bug: variable named "end"


I believe this is to do with the code and not a bug. The code you gave
segfault'ed and dumped the core, on a machine close to your arc (1.3.12-4).
Im not a c programmer, yet ;), but i think its to do with declaration...This
works:

int
main()
{

  /* declare the variable so main() can see it */
  int end;

  /* do what you please with end */
  int end = 0;

}

Elfyn

----- Original Message -----
From: Takashi Chikayama <chikayama@kjps.net>
To: <cygwin@cygwin.com>
Cc: 'ICPC02' <kurage@cs.meiji.ac.jp>
Sent: Saturday, October 19, 2002 6:16 AM
Subject: 1.3.12: gcc bug: variable named "end"


> CYGWIN_NT-5.1 X22CHIKAYAMA 1.3.12(0.54/3/2) 2002-07-06 02:16 i686
> unknown
> gcc 2.95.3-5
>
> The following program causes a segmentation fault.
> ---
> int end;
> main() { end = 0; }
> ---
> Seems that the problem is with the variable name "end".
> In the object code tries to store in some invalid address.
> Variables with other names, of course, does not cause this.
>
> - Takashi Chikayama@Dept. of Frontier Informatics, the Univ. of Tokyo
> - 7-3-1 Hongo, Bunkyo-ku, Tokyo 113 Japan
> - Tel. +81-3-5841-6658; Fax. +81-3-5841-8572
>
>
>
> --
> 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/
>



--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]