This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Line info causes GCC to bomb?
- From: g6522c at earthlink dot net
- To: cygwin at cygwin dot com
- Date: Sun, 19 Aug 2007 16:23:58 -0400 (GMT-04:00)
- Subject: Line info causes GCC to bomb?
- Reply-to: rkies at cpan dot org
I haven't seen this problem anywhere in the list archive, so
here it is.
This preprocessed input causes GCC (3.4.4) to segfault....
# 1 "test.c" 1
int main () {
return 0;
}
... and this doesn't:
# 1 "test.c"
# 1 "test.c" 1
int main () {
return 0;
}
Am I missing something?
Thanks,
Robert Kiesling
----------------------------------------------------------------------------
Ctalk Project Home Page: http://ctalk-lang.sourceforge.net
Mailing List: ctalk-lang-announce@lists.sourceforge.net
----------------------------------------------------------------------------
----------------------------------------------------------------------------
Ctalk Project Home Page: http://ctalk-lang.sourceforge.net
Mailing List: ctalk-lang-announce@lists.sourceforge.net
----------------------------------------------------------------------------
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/