------- Comment #2 from brad dot finney at humboldt dot edu 2010-09-07 20:55 ------- Subject: Re: ICE on missing module file
burnus at gcc dot gnu dot org wrote: > ------- Comment #1 from burnus at gcc dot gnu dot org 2010-09-07 15:09 > ------- > Works with x86_64-unknown-linux-gnu (4.6.0 20100907 (experimental) [trunk > revision 163943]) > and also under i686-w64-mingw and x86_64-w64-mingw. > > A test with i586-pc-mingw32 is pending; Kai offered to do it. > > Brad, if possible, can you provide more information, i.e. which version of > MinGW32 exactly (if known, for me "gfortran -v" prints the version + the SVN > revision), where did you get the build from? D:\fortran>gfortran -v Using built-in specs. COLLECT_GCC=gfortran COLLECT_LTO_WRAPPER=c:/program files/gfortran/bin/../libexec/gcc/i586-pc-mingw32/4.6.0/lto-wrapper.exe Target: i586-pc-mingw32 Configured with: ../gcc-trunk/configure --prefix=/mingw --enable-languages=c,fortran --with-gmp=/home/brad/gfortran/dependencies --disable-werror --enable-threa ds --disable-nls --build=i586-pc-mingw32 --enable-libgomp --disable-shared --disable-win32-registry --with-dwarf2 --disable-sjlj-exceptions --enable-lto Thread model: win32 gcc version 4.6.0 20100620 (experimental) [trunk revision 161045] (GCC) I am fighting with gdb, and it is winning. I will try that part later. Brad > > Can you run the compiler in a debugger? Use: > gfortran -v bugtest.f90 > and search for the line with starts with /some/path/f95 and run then the > "f951" > line in a debugger, e.g. > gdb --args /some/path/to/f951 many, many, many options > and then in (gdb) > run > bt > and post the result of the backtrace (bt). > > -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45575
