According to Olivier Lecarme:
It does exist. :-)
In fact we have a bug reporting system: See the page "bugs" on our WWW site,
http://home.pages.de/~gnu-pascal/
but actually most bug reports go through this list, so you did it right. I expect that the mail reporting system will become more useful when GPC is getting more stable and we will fine-tune the compiler.
Alpha versions of GPC have an option "-dY" which tells GPC to echo each source line to stderr. Then you can see where in the source GPC crashes.
Another interesting option in this context is "-dy" which lets GPC output parsing debugging information. If you post the last "rule" listed there, e.g.
Reducing via rule 616 (line 3782), variable_or_function_access_maybe_assignment rest_of_statement -> assignment_or_call_statement
it might already tell me something about the error. (The line number refers to the GPC source file `gpc-parse.y'.)
This I don't understand ... could you please explain what you mean by "physical" and "logical"?
Perhaps it's an alignment problem? Within records, GPC aligns Integers on 4-byte boundaries, etc.
Greetings,
Peter
Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski@uni-essen.de - http://home.pages.de/~peter.gerwinski/ [970201] maintainer GNU Pascal - http://home.pages.de/~gnu-pascal/ [970125]