bug in GPC 2.0_(re)

Sun, 30 Mar 1997 00:01:54 +0100

----------
| Von: Olivier Lecarme 
| An: bug-gpc@prep.ai.mit.edu
| Cc: ol@clio.unice.fr; gpc-request@hut.fi
| Betreff: bug in GPC 2.0
| Datum: Samstag, 29. M=E4rz 1997 21:53
|=20
| I get the following message when compiling a somewhat complicated
| program (2352 lines):
|=20
| gpc: Internal compiler error: program gpc1 got fatal signal 6
|=20
| What can I do? Send you the whole program would probably be useless. Ar=
e
| there some options I could trigger in order to get more information?
|=20
| By the way, I encountered another problem with GPC: one program writes =
a
| file of some complicated record type; another program reads this file,
| declared in exactly the same way. However, it seems that every get(file=
)
| skips to the next *physical* record, instead of the next logical one.
|=20
| Did anybody encounter the same problem?
|=20
| --=20
| 			Olivier Lecarme
|=20


Hi Oliver,

I've had problems like your's too. (Ok, was fatal signal 11). Usually
they were forced by syntactical errors or incorrectly handled keywords.
(Somewhere in the documentation you can find a sentence as "a stable
compiler never catches fatal signals" - these are bugs in the compiler)

IMHO you should try out the latest developer alpha-release, may be its
somewhat more stable, isn't it?

Sven Engelhardt
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Sven Engelhardt             http://www.sik.de               se@sik.de



Sven Engelhardt (sven@sik.de)