Hi,
I use "gpc version 19991030, based on 2.95.2 19991024 (release)" on an Intel-Linux computer (suse 7.0) and have encountered the following problems:
1. When I accidentally have a pascal source code with a uses-statement that includes a unit with the name of the sourcecode file itself I get an endless loop when compiling it with --automake or --autobild. The compiler uses all memory available. example: A file called "test.pas" containing "uses test;" statement.
2. When I upgraded to the above mentioned version of the compiler I got an "Internal compiler error: program gpc1 got fatal signal 11" when I compiled without --autobuild and had old gpi- and object-files around. A more descriptive error message would be nice.
Sven
Sven Sahle wrote:
I use "gpc version 19991030, based on 2.95.2 19991024 (release)" on an Intel-Linux computer (suse 7.0) and have encountered the following problems:
- When I accidentally have a pascal source code with a uses-statement
that includes a unit with the name of the sourcecode file itself I get an endless loop when compiling it with --automake or --autobild. The compiler uses all memory available. example: A file called "test.pas" containing "uses test;" statement.
Thanks for the report. I thought that'd been fixed, but the problem is still there indeed...
Ah, it only seems to happen if the file has no `program', `unit' or `module' header, strange... (sven18.pas)
- When I upgraded to the above mentioned version of the compiler I got
an "Internal compiler error: program gpc1 got fatal signal 11" when I compiled without --autobuild and had old gpi- and object-files around. A more descriptive error message would be nice.
Yes... :-(
Frank
-
Frank Heckenbach -
Sven Sahle