[Bug fortran/45575] ICE on missing module file

2010-09-10 Thread fxcoudert at gcc dot gnu dot org


--- Comment #6 from fxcoudert at gcc dot gnu dot org  2010-09-10 21:40 
---


*** This bug has been marked as a duplicate of 31519 ***


-- 

fxcoudert at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45575



[Bug fortran/45575] ICE on missing module file

2010-09-08 Thread ubizjak at gmail dot com


--- Comment #5 from ubizjak at gmail dot com  2010-09-08 09:18 ---
(In reply to comment #1)

 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).

You should also break fatal_error in between run and bt command.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45575



[Bug fortran/45575] ICE on missing module file

2010-09-07 Thread burnus at gcc dot gnu dot org


--- 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?

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).


-- 

burnus at gcc dot gnu dot org changed:

   What|Removed |Added

   Keywords||ice-on-invalid-code


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45575



[Bug fortran/45575] ICE on missing module file

2010-09-07 Thread brad dot finney at humboldt dot edu


--- 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:\fortrangfortran -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



[Bug fortran/45575] ICE on missing module file

2010-09-07 Thread brad dot finney at humboldt dot edu


--- Comment #3 from brad dot finney at humboldt dot edu  2010-09-08 04:32 
---
Subject: Re:  ICE on missing module file



On 9/7/2010 8:09 AM, 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?

 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).




Don't think this produced any useful information, but here is the gdb 
output

F:\brad\class\engr325gdb --args 
d:/gfortran/bin/../libexec/gcc/i586-pc-mingw32/4.6.0/f951.exe 
bugtest.f90 -quiet -dumpbase bugtest.f90 -mtune=pentium -march=pentium 
-auxbase bugtest -version -fintrinsic-modules-path 
d:/gfortran/bin/../lib/gcc/i586-pc-mingw32/4.6.0/finclude -o C:\tem
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as i686-pc-mingw32...
(no debugging symbols found)
(gdb) run
Starting program: 
d:/gfortran/bin/../libexec/gcc/i586-pc-mingw32/4.6.0/f951.exe 
bugtest.f90 -quiet -dumpbase bugtest.f90 -mtune=pentium -march=pentium 
-auxbase bugtest -version -fintrinsic-modules-path 
d:/gfortran/bin/../lib/gcc/i586-pc-mingw32/4.6.0/finclude -o 
C:\\temp\\bugtest.s
[New thread 2108.0x908]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
GNU Fortran (GCC) version 4.6.0 20100620 (experimental) [trunk revision 
161045] (i586-pc-mingw32)
 compiled by GNU C version 4.6.0 20100620 (experimental) [trunk 
revision 161045], GMP version 4.3.2, MPFR version 2.4.2, MPC version 0.8.2
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
GNU Fortran (GCC) version 4.6.0 20100620 (experimental) [trunk revision 
161045] (i586-pc-mingw32)
 compiled by GNU C version 4.6.0 20100620 (experimental) [trunk 
revision 161045], GMP version 4.3.2, MPFR version 2.4.2, MPC version 0.8.2
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
bugtest.f90:2.13:

   use mytypes
  1
Fatal Error: Can't open module file 'mytypes.mod' for reading at (1): No 
such file or directory

Program exited with code 03.
(gdb) bt
No stack.
(gdb)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45575



[Bug fortran/45575] ICE on missing module file

2010-09-07 Thread brad dot finney at humboldt dot edu


--- Comment #4 from brad dot finney at humboldt dot edu  2010-09-08 04:46 
---
Subject: Re:  ICE on missing module file



On 9/7/2010 8:09 AM, 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?

Forgot to add, I built this version myself.

Brad


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45575