[mpich-discuss] cygwin & mingw64 & windows 7 (64bits)

Jean-Michel Beuken Jean-Michel.beuken at uclouvain.be
Tue Nov 9 08:42:43 CST 2010


Hello,

On 08/11/2010 22:32, Jayesh Krishna wrote:
> Hi,
>   From the error code it looks like access violation. Can you try running the executable from a mingw bash prompt ?
>   I will also try installing mingw 64-bit at the lab and let you know the results.
for info :

I install TDM-GCC (64bits) and I have the sames symptomes but the gdb works in ssh/bash environement  :

-------
gfortran -g -IC:\\mpich2\\include -c pi3f90.f90 -fno-range-check -fsecond-underscore
gfortran -g -o pi3f90 pi3f90.o -LC:\\mpich2\\lib -lfmpich2g  -lmpi
-------

-------
$ gdb pi3f90.exe
GNU gdb (GDB) 7.1
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This GDB was configured as "x86_64-w64-mingw32".
Reading symbols from C:\Users\buildbot\Desktop\WorkSpace/pi3f90.exe...done.
(gdb) run
Starting program: C:\Users\buildbot\Desktop\WorkSpace/pi3f90.exe
[New Thread 1984.0xa30]

Program received signal SIGSEGV, Segmentation fault.
0x0000000000401960 in mpi_init__ ()
(gdb) where
#0  0x0000000000401960 in mpi_init__ ()
#1  0x00000000004015be in MAIN__ () at pi3f90.f90:37
-------

-------
$ gdb --args c:\\mpich2\\bin\\mpiexec.exe -n 4 -exitcodes pi3f90.exe
GNU gdb (GDB) 7.1
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This GDB was configured as "x86_64-w64-mingw32".
Reading symbols from c:\mpich2\bin\mpiexec.exe...(no debugging symbols found)...done.
(gdb) run
Starting program: c:\mpich2\bin\mpiexec.exe -n 4 -exitcodes pi3f90.exe
[New Thread 2608.0xba8]
[New Thread 2608.0x78]
rank: node: exit code
0: woopy.pcpm.ucl.ac.be: -1073741515
1: woopy.pcpm.ucl.ac.be: -1073741515
2: woopy.pcpm.ucl.ac.be: -1073741515
3: woopy.pcpm.ucl.ac.be: -1073741515
[New Thread 2608.0xd08]

Program exited with code 030000000465.
(gdb) where
(gdb) No stack.
----------------

regards

jmb



More information about the mpich-discuss mailing list