On 13 January 2011 08:44, Schmidt, Steffen wrote: > > Hello, > > I'm using GNU Toolchain cross-compiler MinGW32 to mips32 in GCC version 4.3.2 > > During compilation I rarely get a mysterious "internal compiler error: Segmentation fault" in GCC. This segmentation fault seems somehow to be related to the environment GCC runs in, e.g. the path where GCC is started in, environment variables or compiler parameters. If the segmentation fault occurs when compiling a certain c file, it is reproducible, as long as I do not change the file or the environment GCC runs in. If I change e.g. the path to the file, by renaming a folder, the segmentation fault is gone. I've also found, that by adding a certain amount of whitespaces to the c file (spaces or new lines) without changing anything else in the c file and changing nothing in the environment GCC runs in, the segmentation fault is also gone. > > Unfortunately, I did not compile this GCC by myself, it has no debug information, and recompilation of this GCC or an update to a newer GCC version is currently not an option for me either. Is there perhaps some way to get more detailed information about the GCC crash, by using the GCC as is, without recompilation, like some debug option on GCCs command line? I need something that would help me trace the error, so that I might be able to prevent the crash from happening and to submit a bug report. The -v option will show you the sub-processes that the gcc driver runs, then you can try debugging that process, see http://gcc.gnu.org/wiki/DebuggingGCC
