Prof A Olowofoyeku (The African Chief) wrote:
Unfortunately, running gpc1 directly (either in gdb or outside of it, with or without parameters) causes an ICE. "gpc -v" doesn't tell me how to run gpc1 correctly.
One thing about terminology: "true" ICE is when the compiler detects an error and writes error message. Those messages normally include exact source location (line number and file) of the error, which helps quite a lot in fixing them. Another thing is segmentation fault. If you get segmentation fault it means that you can reporduce the bug inside debugger. The debugger should catch the fault, you can then type `bt' to get the bactrace. It is possible that mingw is doing something strange, so that the segmentation fault is caught by gpc1.exe, then you need to set breakpoint inside `internal_error': break internal_error
Also, it is possible that you get an error deeply inside automake. The simplest way then is to find which unit is crashing, compile all its imports with `--interface-only' and then try to compile the causing the crash. By the way: the crash may be in automake machinery (what you wrote suggest otherwise, by just in case I will mention this). Then you need to give `-fautomake' option to gpc1.exe, and additionaly -famtmpfile=fooo option (where `fooo' is a name of existing empty file).
One general remark: when you give an option with to dashes to gpc, you need to use `-f' to gpc1. For example: `--objects-are-references' has to be written as `-fobjects-are-references'. gpc accepts both versions, but convets the first ionto the second one. gpc1 accepts only the second version.